Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler.
Number of rules (primarily dangerous function names) in C/C++ ruleset: 223
Examining data/anope-2.0.9/include/access.h
Examining data/anope-2.0.9/include/account.h
Examining data/anope-2.0.9/include/anope.h
Examining data/anope-2.0.9/include/base.h
Examining data/anope-2.0.9/include/bots.h
Examining data/anope-2.0.9/include/channels.h
Examining data/anope-2.0.9/include/commands.h
Examining data/anope-2.0.9/include/config.h
Examining data/anope-2.0.9/include/defs.h
Examining data/anope-2.0.9/include/extensible.h
Examining data/anope-2.0.9/include/hashcomp.h
Examining data/anope-2.0.9/include/language.h
Examining data/anope-2.0.9/include/lists.h
Examining data/anope-2.0.9/include/logger.h
Examining data/anope-2.0.9/include/mail.h
Examining data/anope-2.0.9/include/memo.h
Examining data/anope-2.0.9/include/messages.h
Examining data/anope-2.0.9/include/modes.h
Examining data/anope-2.0.9/include/module.h
Examining data/anope-2.0.9/include/modules.h
Examining data/anope-2.0.9/include/modules/bs_badwords.h
Examining data/anope-2.0.9/include/modules/bs_kick.h
Examining data/anope-2.0.9/include/modules/cs_entrymsg.h
Examining data/anope-2.0.9/include/modules/cs_log.h
Examining data/anope-2.0.9/include/modules/cs_mode.h
Examining data/anope-2.0.9/include/modules/dns.h
Examining data/anope-2.0.9/include/modules/encryption.h
Examining data/anope-2.0.9/include/modules/httpd.h
Examining data/anope-2.0.9/include/modules/ldap.h
Examining data/anope-2.0.9/include/modules/ns_cert.h
Examining data/anope-2.0.9/include/modules/os_forbid.h
Examining data/anope-2.0.9/include/modules/os_ignore.h
Examining data/anope-2.0.9/include/modules/os_news.h
Examining data/anope-2.0.9/include/modules/os_session.h
Examining data/anope-2.0.9/include/modules/pseudoclients/chanserv.h
Examining data/anope-2.0.9/include/modules/pseudoclients/global.h
Examining data/anope-2.0.9/include/modules/pseudoclients/memoserv.h
Examining data/anope-2.0.9/include/modules/pseudoclients/nickserv.h
Examining data/anope-2.0.9/include/modules/redis.h
Examining data/anope-2.0.9/include/modules/sasl.h
Examining data/anope-2.0.9/include/modules/set_misc.h
Examining data/anope-2.0.9/include/modules/sql.h
Examining data/anope-2.0.9/include/modules/ssl.h
Examining data/anope-2.0.9/include/modules/suspend.h
Examining data/anope-2.0.9/include/modules/xmlrpc.h
Examining data/anope-2.0.9/include/opertype.h
Examining data/anope-2.0.9/include/protocol.h
Examining data/anope-2.0.9/include/pstdint.h
Examining data/anope-2.0.9/include/regchannel.h
Examining data/anope-2.0.9/include/regexpr.h
Examining data/anope-2.0.9/include/serialize.h
Examining data/anope-2.0.9/include/servers.h
Examining data/anope-2.0.9/include/service.h
Examining data/anope-2.0.9/include/services.h
Examining data/anope-2.0.9/include/socketengine.h
Examining data/anope-2.0.9/include/sockets.h
Examining data/anope-2.0.9/include/threadengine.h
Examining data/anope-2.0.9/include/timers.h
Examining data/anope-2.0.9/include/uplink.h
Examining data/anope-2.0.9/include/users.h
Examining data/anope-2.0.9/include/version.cpp
Examining data/anope-2.0.9/include/xline.h
Examining data/anope-2.0.9/modules/bs_autoassign.cpp
Examining data/anope-2.0.9/modules/commands/bs_assign.cpp
Examining data/anope-2.0.9/modules/commands/bs_badwords.cpp
Examining data/anope-2.0.9/modules/commands/bs_bot.cpp
Examining data/anope-2.0.9/modules/commands/bs_botlist.cpp
Examining data/anope-2.0.9/modules/commands/bs_control.cpp
Examining data/anope-2.0.9/modules/commands/bs_info.cpp
Examining data/anope-2.0.9/modules/commands/bs_kick.cpp
Examining data/anope-2.0.9/modules/commands/bs_set.cpp
Examining data/anope-2.0.9/modules/commands/cs_access.cpp
Examining data/anope-2.0.9/modules/commands/cs_akick.cpp
Examining data/anope-2.0.9/modules/commands/cs_ban.cpp
Examining data/anope-2.0.9/modules/commands/cs_clone.cpp
Examining data/anope-2.0.9/modules/commands/cs_drop.cpp
Examining data/anope-2.0.9/modules/commands/cs_enforce.cpp
Examining data/anope-2.0.9/modules/commands/cs_entrymsg.cpp
Examining data/anope-2.0.9/modules/commands/cs_flags.cpp
Examining data/anope-2.0.9/modules/commands/cs_getkey.cpp
Examining data/anope-2.0.9/modules/commands/cs_info.cpp
Examining data/anope-2.0.9/modules/commands/cs_invite.cpp
Examining data/anope-2.0.9/modules/commands/cs_kick.cpp
Examining data/anope-2.0.9/modules/commands/cs_list.cpp
Examining data/anope-2.0.9/modules/commands/cs_log.cpp
Examining data/anope-2.0.9/modules/commands/cs_mode.cpp
Examining data/anope-2.0.9/modules/commands/cs_register.cpp
Examining data/anope-2.0.9/modules/commands/cs_seen.cpp
Examining data/anope-2.0.9/modules/commands/cs_set.cpp
Examining data/anope-2.0.9/modules/commands/cs_set_misc.cpp
Examining data/anope-2.0.9/modules/commands/cs_status.cpp
Examining data/anope-2.0.9/modules/commands/cs_suspend.cpp
Examining data/anope-2.0.9/modules/commands/cs_sync.cpp
Examining data/anope-2.0.9/modules/commands/cs_topic.cpp
Examining data/anope-2.0.9/modules/commands/cs_unban.cpp
Examining data/anope-2.0.9/modules/commands/cs_updown.cpp
Examining data/anope-2.0.9/modules/commands/cs_xop.cpp
Examining data/anope-2.0.9/modules/commands/gl_global.cpp
Examining data/anope-2.0.9/modules/commands/greet.cpp
Examining data/anope-2.0.9/modules/commands/help.cpp
Examining data/anope-2.0.9/modules/commands/hs_del.cpp
Examining data/anope-2.0.9/modules/commands/hs_group.cpp
Examining data/anope-2.0.9/modules/commands/hs_list.cpp
Examining data/anope-2.0.9/modules/commands/hs_off.cpp
Examining data/anope-2.0.9/modules/commands/hs_on.cpp
Examining data/anope-2.0.9/modules/commands/hs_request.cpp
Examining data/anope-2.0.9/modules/commands/hs_set.cpp
Examining data/anope-2.0.9/modules/commands/ms_cancel.cpp
Examining data/anope-2.0.9/modules/commands/ms_check.cpp
Examining data/anope-2.0.9/modules/commands/ms_del.cpp
Examining data/anope-2.0.9/modules/commands/ms_ignore.cpp
Examining data/anope-2.0.9/modules/commands/ms_info.cpp
Examining data/anope-2.0.9/modules/commands/ms_list.cpp
Examining data/anope-2.0.9/modules/commands/ms_read.cpp
Examining data/anope-2.0.9/modules/commands/ms_rsend.cpp
Examining data/anope-2.0.9/modules/commands/ms_send.cpp
Examining data/anope-2.0.9/modules/commands/ms_sendall.cpp
Examining data/anope-2.0.9/modules/commands/ms_set.cpp
Examining data/anope-2.0.9/modules/commands/ms_staff.cpp
Examining data/anope-2.0.9/modules/commands/ns_access.cpp
Examining data/anope-2.0.9/modules/commands/ns_ajoin.cpp
Examining data/anope-2.0.9/modules/commands/ns_alist.cpp
Examining data/anope-2.0.9/modules/commands/ns_cert.cpp
Examining data/anope-2.0.9/modules/commands/ns_drop.cpp
Examining data/anope-2.0.9/modules/commands/ns_getemail.cpp
Examining data/anope-2.0.9/modules/commands/ns_getpass.cpp
Examining data/anope-2.0.9/modules/commands/ns_group.cpp
Examining data/anope-2.0.9/modules/commands/ns_identify.cpp
Examining data/anope-2.0.9/modules/commands/ns_info.cpp
Examining data/anope-2.0.9/modules/commands/ns_list.cpp
Examining data/anope-2.0.9/modules/commands/ns_logout.cpp
Examining data/anope-2.0.9/modules/commands/ns_recover.cpp
Examining data/anope-2.0.9/modules/commands/ns_register.cpp
Examining data/anope-2.0.9/modules/commands/ns_resetpass.cpp
Examining data/anope-2.0.9/modules/commands/ns_set.cpp
Examining data/anope-2.0.9/modules/commands/ns_set_misc.cpp
Examining data/anope-2.0.9/modules/commands/ns_status.cpp
Examining data/anope-2.0.9/modules/commands/ns_suspend.cpp
Examining data/anope-2.0.9/modules/commands/ns_update.cpp
Examining data/anope-2.0.9/modules/commands/os_akill.cpp
Examining data/anope-2.0.9/modules/commands/os_chankill.cpp
Examining data/anope-2.0.9/modules/commands/os_config.cpp
Examining data/anope-2.0.9/modules/commands/os_defcon.cpp
Examining data/anope-2.0.9/modules/commands/os_dns.cpp
Examining data/anope-2.0.9/modules/commands/os_forbid.cpp
Examining data/anope-2.0.9/modules/commands/os_ignore.cpp
Examining data/anope-2.0.9/modules/commands/os_info.cpp
Examining data/anope-2.0.9/modules/commands/os_jupe.cpp
Examining data/anope-2.0.9/modules/commands/os_kick.cpp
Examining data/anope-2.0.9/modules/commands/os_kill.cpp
Examining data/anope-2.0.9/modules/commands/os_list.cpp
Examining data/anope-2.0.9/modules/commands/os_login.cpp
Examining data/anope-2.0.9/modules/commands/os_logsearch.cpp
Examining data/anope-2.0.9/modules/commands/os_mode.cpp
Examining data/anope-2.0.9/modules/commands/os_modinfo.cpp
Examining data/anope-2.0.9/modules/commands/os_module.cpp
Examining data/anope-2.0.9/modules/commands/os_news.cpp
Examining data/anope-2.0.9/modules/commands/os_noop.cpp
Examining data/anope-2.0.9/modules/commands/os_oline.cpp
Examining data/anope-2.0.9/modules/commands/os_oper.cpp
Examining data/anope-2.0.9/modules/commands/os_reload.cpp
Examining data/anope-2.0.9/modules/commands/os_session.cpp
Examining data/anope-2.0.9/modules/commands/os_set.cpp
Examining data/anope-2.0.9/modules/commands/os_shutdown.cpp
Examining data/anope-2.0.9/modules/commands/os_stats.cpp
Examining data/anope-2.0.9/modules/commands/os_svs.cpp
Examining data/anope-2.0.9/modules/commands/os_sxline.cpp
Examining data/anope-2.0.9/modules/commands/os_update.cpp
Examining data/anope-2.0.9/modules/cs_statusupdate.cpp
Examining data/anope-2.0.9/modules/database/db_flatfile.cpp
Examining data/anope-2.0.9/modules/database/db_old.cpp
Examining data/anope-2.0.9/modules/database/db_redis.cpp
Examining data/anope-2.0.9/modules/database/db_sql.cpp
Examining data/anope-2.0.9/modules/database/db_sql_live.cpp
Examining data/anope-2.0.9/modules/encryption/enc_bcrypt.cpp
Examining data/anope-2.0.9/modules/encryption/enc_md5.cpp
Examining data/anope-2.0.9/modules/encryption/enc_none.cpp
Examining data/anope-2.0.9/modules/encryption/enc_old.cpp
Examining data/anope-2.0.9/modules/encryption/enc_sha1.cpp
Examining data/anope-2.0.9/modules/encryption/enc_sha256.cpp
Examining data/anope-2.0.9/modules/extra/m_ldap.cpp
Examining data/anope-2.0.9/modules/extra/m_ldap_authentication.cpp
Examining data/anope-2.0.9/modules/extra/m_ldap_oper.cpp
Examining data/anope-2.0.9/modules/extra/m_mysql.cpp
Examining data/anope-2.0.9/modules/extra/m_regex_pcre.cpp
Examining data/anope-2.0.9/modules/extra/m_regex_posix.cpp
Examining data/anope-2.0.9/modules/extra/m_regex_tre.cpp
Examining data/anope-2.0.9/modules/extra/m_sql_authentication.cpp
Examining data/anope-2.0.9/modules/extra/m_sql_log.cpp
Examining data/anope-2.0.9/modules/extra/m_sql_oper.cpp
Examining data/anope-2.0.9/modules/extra/m_sqlite.cpp
Examining data/anope-2.0.9/modules/extra/m_ssl_gnutls.cpp
Examining data/anope-2.0.9/modules/extra/m_ssl_openssl.cpp
Examining data/anope-2.0.9/modules/extra/stats/cs_fantasy_stats.cpp
Examining data/anope-2.0.9/modules/extra/stats/cs_fantasy_top.cpp
Examining data/anope-2.0.9/modules/extra/stats/irc2sql/irc2sql.cpp
Examining data/anope-2.0.9/modules/extra/stats/irc2sql/irc2sql.h
Examining data/anope-2.0.9/modules/extra/stats/irc2sql/tables.cpp
Examining data/anope-2.0.9/modules/extra/stats/irc2sql/utils.cpp
Examining data/anope-2.0.9/modules/extra/stats/m_chanstats.cpp
Examining data/anope-2.0.9/modules/fantasy.cpp
Examining data/anope-2.0.9/modules/m_dns.cpp
Examining data/anope-2.0.9/modules/m_dnsbl.cpp
Examining data/anope-2.0.9/modules/m_helpchan.cpp
Examining data/anope-2.0.9/modules/m_httpd.cpp
Examining data/anope-2.0.9/modules/m_proxyscan.cpp
Examining data/anope-2.0.9/modules/m_redis.cpp
Examining data/anope-2.0.9/modules/m_rewrite.cpp
Examining data/anope-2.0.9/modules/m_sasl.cpp
Examining data/anope-2.0.9/modules/m_xmlrpc.cpp
Examining data/anope-2.0.9/modules/m_xmlrpc_main.cpp
Examining data/anope-2.0.9/modules/ns_maxemail.cpp
Examining data/anope-2.0.9/modules/protocol/bahamut.cpp
Examining data/anope-2.0.9/modules/protocol/charybdis.cpp
Examining data/anope-2.0.9/modules/protocol/hybrid.cpp
Examining data/anope-2.0.9/modules/protocol/inspircd12.cpp
Examining data/anope-2.0.9/modules/protocol/inspircd20.cpp
Examining data/anope-2.0.9/modules/protocol/inspircd3.cpp
Examining data/anope-2.0.9/modules/protocol/ngircd.cpp
Examining data/anope-2.0.9/modules/protocol/plexus.cpp
Examining data/anope-2.0.9/modules/protocol/ratbox.cpp
Examining data/anope-2.0.9/modules/protocol/unreal.cpp
Examining data/anope-2.0.9/modules/protocol/unreal4.cpp
Examining data/anope-2.0.9/modules/pseudoclients/botserv.cpp
Examining data/anope-2.0.9/modules/pseudoclients/chanserv.cpp
Examining data/anope-2.0.9/modules/pseudoclients/global.cpp
Examining data/anope-2.0.9/modules/pseudoclients/hostserv.cpp
Examining data/anope-2.0.9/modules/pseudoclients/memoserv.cpp
Examining data/anope-2.0.9/modules/pseudoclients/nickserv.cpp
Examining data/anope-2.0.9/modules/pseudoclients/operserv.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/access.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/access.h
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/akick.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/akick.h
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/drop.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/drop.h
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/info.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/info.h
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/modes.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/modes.h
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/set.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/set.h
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/utils.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/chanserv/utils.h
Examining data/anope-2.0.9/modules/webcpanel/pages/confirm.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/confirm.h
Examining data/anope-2.0.9/modules/webcpanel/pages/hostserv/request.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/hostserv/request.h
Examining data/anope-2.0.9/modules/webcpanel/pages/index.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/index.h
Examining data/anope-2.0.9/modules/webcpanel/pages/logout.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/logout.h
Examining data/anope-2.0.9/modules/webcpanel/pages/memoserv/memos.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/memoserv/memos.h
Examining data/anope-2.0.9/modules/webcpanel/pages/nickserv/access.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/nickserv/access.h
Examining data/anope-2.0.9/modules/webcpanel/pages/nickserv/alist.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/nickserv/alist.h
Examining data/anope-2.0.9/modules/webcpanel/pages/nickserv/cert.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/nickserv/cert.h
Examining data/anope-2.0.9/modules/webcpanel/pages/nickserv/info.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/nickserv/info.h
Examining data/anope-2.0.9/modules/webcpanel/pages/operserv/akill.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/operserv/akill.h
Examining data/anope-2.0.9/modules/webcpanel/pages/register.cpp
Examining data/anope-2.0.9/modules/webcpanel/pages/register.h
Examining data/anope-2.0.9/modules/webcpanel/static_fileserver.cpp
Examining data/anope-2.0.9/modules/webcpanel/static_fileserver.h
Examining data/anope-2.0.9/modules/webcpanel/template_fileserver.cpp
Examining data/anope-2.0.9/modules/webcpanel/template_fileserver.h
Examining data/anope-2.0.9/modules/webcpanel/webcpanel.cpp
Examining data/anope-2.0.9/modules/webcpanel/webcpanel.h
Examining data/anope-2.0.9/src/access.cpp
Examining data/anope-2.0.9/src/account.cpp
Examining data/anope-2.0.9/src/base.cpp
Examining data/anope-2.0.9/src/base64.cpp
Examining data/anope-2.0.9/src/bots.cpp
Examining data/anope-2.0.9/src/channels.cpp
Examining data/anope-2.0.9/src/command.cpp
Examining data/anope-2.0.9/src/config.cpp
Examining data/anope-2.0.9/src/extensible.cpp
Examining data/anope-2.0.9/src/hashcomp.cpp
Examining data/anope-2.0.9/src/init.cpp
Examining data/anope-2.0.9/src/language.cpp
Examining data/anope-2.0.9/src/logger.cpp
Examining data/anope-2.0.9/src/mail.cpp
Examining data/anope-2.0.9/src/main.cpp
Examining data/anope-2.0.9/src/memos.cpp
Examining data/anope-2.0.9/src/messages.cpp
Examining data/anope-2.0.9/src/misc.cpp
Examining data/anope-2.0.9/src/modes.cpp
Examining data/anope-2.0.9/src/module.cpp
Examining data/anope-2.0.9/src/modulemanager.cpp
Examining data/anope-2.0.9/src/nickalias.cpp
Examining data/anope-2.0.9/src/nickcore.cpp
Examining data/anope-2.0.9/src/opertype.cpp
Examining data/anope-2.0.9/src/pipeengine.cpp
Examining data/anope-2.0.9/src/process.cpp
Examining data/anope-2.0.9/src/protocol.cpp
Examining data/anope-2.0.9/src/regchannel.cpp
Examining data/anope-2.0.9/src/serialize.cpp
Examining data/anope-2.0.9/src/servers.cpp
Examining data/anope-2.0.9/src/siphash.cpp
Examining data/anope-2.0.9/src/socket_clients.cpp
Examining data/anope-2.0.9/src/socket_transport.cpp
Examining data/anope-2.0.9/src/socketengines/socketengine_epoll.cpp
Examining data/anope-2.0.9/src/socketengines/socketengine_kqueue.cpp
Examining data/anope-2.0.9/src/socketengines/socketengine_poll.cpp
Examining data/anope-2.0.9/src/socketengines/socketengine_select.cpp
Examining data/anope-2.0.9/src/sockets.cpp
Examining data/anope-2.0.9/src/threadengine.cpp
Examining data/anope-2.0.9/src/timers.cpp
Examining data/anope-2.0.9/src/tools/anopesmtp.cpp
Examining data/anope-2.0.9/src/uplink.cpp
Examining data/anope-2.0.9/src/users.cpp
Examining data/anope-2.0.9/src/win32/anope_windows.h
Examining data/anope-2.0.9/src/win32/dir/dir.cpp
Examining data/anope-2.0.9/src/win32/dir/dir.h
Examining data/anope-2.0.9/src/win32/dl/dl.cpp
Examining data/anope-2.0.9/src/win32/dl/dl.h
Examining data/anope-2.0.9/src/win32/pipe/pipe.cpp
Examining data/anope-2.0.9/src/win32/pipe/pipe.h
Examining data/anope-2.0.9/src/win32/pthread/pthread.cpp
Examining data/anope-2.0.9/src/win32/pthread/pthread.h
Examining data/anope-2.0.9/src/win32/resource.h
Examining data/anope-2.0.9/src/win32/sigaction/sigaction.cpp
Examining data/anope-2.0.9/src/win32/sigaction/sigaction.h
Examining data/anope-2.0.9/src/win32/socket.cpp
Examining data/anope-2.0.9/src/win32/socket.h
Examining data/anope-2.0.9/src/win32/win32_memory.cpp
Examining data/anope-2.0.9/src/win32/windows.cpp
Examining data/anope-2.0.9/src/xline.cpp
FINAL RESULTS:
data/anope-2.0.9/src/init.cpp:266:4: [5] (race) chown:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchown( ) instead.
chown(lf->filename.c_str(), uid, gid);
data/anope-2.0.9/include/account.h:124:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
std::vector<Anope::string> access;
data/anope-2.0.9/include/anope.h:487:27: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
extern CoreExport string printf(const char *fmt, ...);
data/anope-2.0.9/include/modules.h:623:79: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
virtual void OnAccessDel(ChannelInfo *ci, CommandSource &source, ChanAccess *access) { throw NotImplementedException(); }
data/anope-2.0.9/include/modules.h:630:79: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
virtual void OnAccessAdd(ChannelInfo *ci, CommandSource &source, ChanAccess *access) { throw NotImplementedException(); }
data/anope-2.0.9/include/modules.h:725:52: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
virtual EventReturn OnCheckPriv(const ChanAccess *access, const Anope::string &priv) { throw NotImplementedException(); }
data/anope-2.0.9/include/modules.h:1049:73: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
virtual void OnSetCorrectModes(User *user, Channel *chan, AccessGroup &access, bool &give_modes, bool &take_modes) { throw NotImplementedException(); }
data/anope-2.0.9/include/regchannel.h:54:49: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
Serialize::Checker<std::vector<ChanAccess *> > access; /* List of authorized users */
data/anope-2.0.9/include/regchannel.h:121:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
void AddAccess(ChanAccess *access);
data/anope-2.0.9/modules/commands/bs_assign.cpp:49:35: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (ci->HasExt("BS_NOBOT") || (!access.HasPriv("ASSIGN") && !source.HasPriv("botserv/administration")))
data/anope-2.0.9/modules/commands/bs_assign.cpp:67:20: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
bool override = !access.HasPriv("ASSIGN");
data/anope-2.0.9/modules/commands/bs_assign.cpp:110:53: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!source.HasPriv("botserv/administration") && !access.HasPriv("ASSIGN"))
data/anope-2.0.9/modules/commands/bs_assign.cpp:128:20: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
bool override = !access.HasPriv("ASSIGN");
data/anope-2.0.9/modules/commands/bs_assign.cpp:227:32: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (nobot.HasExt(c->ci) || (!access.HasPriv("ASSIGN") && !source->HasPriv("botserv/administration")))
data/anope-2.0.9/modules/commands/bs_info.cpp:118:17: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return Anope::printf(Language::Translate(source.GetAccount(), _("Allows you to see %s information about a channel or a bot")), source.service->nick.c_str());
data/anope-2.0.9/modules/commands/bs_kick.cpp:805:53: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!source.HasPriv("botserv/administration") && !access.HasPriv("SET"))
data/anope-2.0.9/modules/commands/bs_kick.cpp:820:21: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
bool override = !access.HasPriv("SET");
data/anope-2.0.9/modules/commands/bs_kick.cpp:828:21: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
bool override = !access.HasPriv("SET");
data/anope-2.0.9/modules/commands/bs_kick.cpp:870:53: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!source.HasPriv("botserv/administration") && !access.HasPriv("SET"))
data/anope-2.0.9/modules/commands/bs_kick.cpp:885:21: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
bool override = !access.HasPriv("SET");
data/anope-2.0.9/modules/commands/bs_kick.cpp:893:21: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
bool override = !access.HasPriv("SET");
data/anope-2.0.9/modules/commands/bs_kick.cpp:1084:3: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, sizeof(buf), fmt.c_str(), args);
data/anope-2.0.9/modules/commands/bs_set.cpp:107:53: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!source.HasPriv("botserv/administration") && !access.HasPriv("SET"))
data/anope-2.0.9/modules/commands/bs_set.cpp:135:20: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
bool override = !access.HasPriv("SET");
data/anope-2.0.9/modules/commands/cs_access.cpp:191:23: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if ((!highest || *access >= *highest) && !u_access.founder && !source.HasPriv("chanserv/access/modify"))
data/anope-2.0.9/modules/commands/cs_access.cpp:217:17: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
ci->AddAccess(access);
data/anope-2.0.9/modules/commands/cs_access.cpp:219:41: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
FOREACH_MOD(OnAccessAdd, (ci, source, access));
data/anope-2.0.9/modules/commands/cs_access.cpp:291:40: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if ((!u_highest || *u_highest <= *access) && !ag.founder && !this->override && access->GetAccount() != source.nc)
data/anope-2.0.9/modules/commands/cs_access.cpp:305:44: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
FOREACH_MOD(OnAccessDel, (ci, source, access));
data/anope-2.0.9/modules/commands/cs_access.cpp:306:13: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
delete access;
data/anope-2.0.9/modules/commands/cs_access.cpp:322:94: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access->GetAccount() != source.nc && !u_access.founder && (!highest || *highest <= *access) && !source.HasPriv("chanserv/access/modify"))
data/anope-2.0.9/modules/commands/cs_access.cpp:331:45: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
FOREACH_MOD(OnAccessDel, (ci, source, access));
data/anope-2.0.9/modules/commands/cs_access.cpp:332:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
delete access;
data/anope-2.0.9/modules/commands/cs_flags.cpp:44:56: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
static Anope::string DetermineFlags(const ChanAccess *access)
data/anope-2.0.9/modules/commands/cs_flags.cpp:152:23: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (*highest <= *access)
data/anope-2.0.9/modules/commands/cs_flags.cpp:163:15: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
current = access;
data/anope-2.0.9/modules/commands/cs_flags.cpp:164:63: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
Anope::string cur_flags = FlagsChanAccess::DetermineFlags(access);
data/anope-2.0.9/modules/commands/cs_flags.cpp:273:17: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
ci->AddAccess(access);
data/anope-2.0.9/modules/commands/cs_flags.cpp:275:41: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
FOREACH_MOD(OnAccessAdd, (ci, source, access));
data/anope-2.0.9/modules/commands/cs_flags.cpp:307:65: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
const Anope::string &flags = FlagsChanAccess::DetermineFlags(access);
data/anope-2.0.9/modules/commands/cs_mode.cpp:888:19: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return Anope::printf(Language::Translate(source.GetAccount(), _("Gives you or the specified nick %s status on a channel")), m.second.c_str());
data/anope-2.0.9/modules/commands/cs_mode.cpp:890:19: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return Anope::printf(Language::Translate(source.GetAccount(), _("Removes %s status from you or the specified nick on a channel")), m.second.c_str());
data/anope-2.0.9/modules/commands/cs_seen.cpp:303:26: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
onlinestatus = Anope::printf(Language::Translate(source.nc, _(" but %s mysteriously dematerialized.")), target.c_str());
data/anope-2.0.9/modules/commands/cs_seen.cpp:317:27: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
onlinestatus = Anope::printf(Language::Translate(source.nc, _(". %s is still online.")), u2->nick.c_str());
data/anope-2.0.9/modules/commands/cs_seen.cpp:319:27: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
onlinestatus = Anope::printf(Language::Translate(source.nc, _(", but %s mysteriously dematerialized.")), info->nick2.c_str());
data/anope-2.0.9/modules/commands/cs_set.cpp:1265:65: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
void OnSetCorrectModes(User *user, Channel *chan, AccessGroup &access, bool &give_modes, bool &take_modes) anope_override
data/anope-2.0.9/modules/commands/cs_xop.cpp:50:56: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
static Anope::string DetermineLevel(const ChanAccess *access)
data/anope-2.0.9/modules/commands/cs_xop.cpp:54:84: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
const XOPChanAccess *xaccess = anope_dynamic_static_cast<const XOPChanAccess *>(access);
data/anope-2.0.9/modules/commands/cs_xop.cpp:117:31: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
const ChanAccess *highest = access.Highest();
data/anope-2.0.9/modules/commands/cs_xop.cpp:124:8: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access.founder && (!access.HasPriv("ACCESS_CHANGE") || cmd_it <= access_it))
data/anope-2.0.9/modules/commands/cs_xop.cpp:124:28: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access.founder && (!access.HasPriv("ACCESS_CHANGE") || cmd_it <= access_it))
data/anope-2.0.9/modules/commands/cs_xop.cpp:187:42: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if ((!highest || *a >= *highest) && !access.founder && !source.HasPriv("chanserv/access/modify"))
data/anope-2.0.9/modules/commands/cs_xop.cpp:246:31: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
const ChanAccess *highest = access.Highest();
data/anope-2.0.9/modules/commands/cs_xop.cpp:264:40: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!mask.equals_ci(nc->display) && !access.founder && (!access.HasPriv("ACCESS_CHANGE") || cmd_it <= access_it))
data/anope-2.0.9/modules/commands/cs_xop.cpp:264:60: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!mask.equals_ci(nc->display) && !access.founder && (!access.HasPriv("ACCESS_CHANGE") || cmd_it <= access_it))
data/anope-2.0.9/modules/commands/cs_xop.cpp:364:8: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!access.HasPriv("ACCESS_LIST") && !source.HasPriv("chanserv/access/list"))
data/anope-2.0.9/modules/commands/cs_xop.cpp:489:17: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return Anope::printf(Language::Translate(source.GetAccount(), _("Modify the list of %s users")), source.command.upper().c_str());
data/anope-2.0.9/modules/commands/ms_read.cpp:35:31: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
Anope::string text = Anope::printf(Language::Translate(na->nc, _("\002[auto-memo]\002 The memo you sent to %s has been viewed.")), targ.c_str());
data/anope-2.0.9/modules/commands/ns_access.cpp:31:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (nc->access.size() >= Config->GetModule(this->owner)->Get<unsigned>("accessmax", "32"))
data/anope-2.0.9/modules/commands/ns_access.cpp:81:11: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (nc->access.empty())
data/anope-2.0.9/modules/commands/ns_access.cpp:88:25: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
for (i = 0, end = nc->access.size(); i < end; ++i)
data/anope-2.0.9/modules/commands/ns_access.cpp:91:39: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (!mask.empty() && !Anope::Match(access, mask))
data/anope-2.0.9/modules/commands/ns_access.cpp:93:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
source.Reply(" %s", access.c_str());
data/anope-2.0.9/modules/commands/ns_alist.cpp:82:8: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access.empty())
data/anope-2.0.9/modules/commands/ns_alist.cpp:89:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
for (unsigned j = 0; j < access.paths.size(); ++j)
data/anope-2.0.9/modules/commands/ns_alist.cpp:91:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
ChanAccess::Path &p = access.paths[j];
data/anope-2.0.9/modules/commands/ns_set.cpp:1284:65: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
void OnSetCorrectModes(User *user, Channel *chan, AccessGroup &access, bool &give_modes, bool &take_modes) anope_override
data/anope-2.0.9/modules/commands/os_defcon.cpp:136:49: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
GlobalService->SendGlobal(NULL, "", Anope::printf(Language::Translate(_("The Defcon level is now at: \002%d\002")), DConfig.defaultlevel));
data/anope-2.0.9/modules/commands/os_forbid.cpp:304:24: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
reason = Anope::printf(Language::Translate(u, _("This channel has been forbidden: %s")), d->reason.c_str());
data/anope-2.0.9/modules/commands/os_forbid.cpp:496:20: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
reason = Anope::printf(Language::Translate(u, _("This channel has been forbidden: %s")), d->reason.c_str());
data/anope-2.0.9/modules/commands/os_login.cpp:60:17: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return Anope::printf(Language::Translate(source.GetAccount(), _("Login to %s")), source.service->nick.c_str());
data/anope-2.0.9/modules/commands/os_login.cpp:102:17: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return Anope::printf(Language::Translate(source.GetAccount(), _("Logout from %s")), source.service->nick.c_str());
data/anope-2.0.9/modules/commands/os_sxline.cpp:233:17: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return Anope::printf(Language::Translate(source.GetAccount(), _("Manipulate the %s list")), source.command.upper().c_str());
data/anope-2.0.9/modules/cs_statusupdate.cpp:19:65: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
void OnAccessAdd(ChannelInfo *ci, CommandSource &, ChanAccess *access) anope_override
data/anope-2.0.9/modules/cs_statusupdate.cpp:42:65: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
void OnAccessDel(ChannelInfo *ci, CommandSource &, ChanAccess *access) anope_override
data/anope-2.0.9/modules/database/db_old.cpp:572:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
nc->access.push_back(buffer);
data/anope-2.0.9/modules/database/db_old.cpp:871:10: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access)
data/anope-2.0.9/modules/database/db_old.cpp:876:10: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access)
data/anope-2.0.9/modules/database/db_old.cpp:902:10: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access)
data/anope-2.0.9/modules/database/db_old.cpp:906:10: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access)
data/anope-2.0.9/modules/database/db_old.cpp:912:21: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
ci->AddAccess(access);
data/anope-2.0.9/modules/pseudoclients/botserv.cpp:31:65: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
void OnSetCorrectModes(User *user, Channel *chan, AccessGroup &access, bool &give_modes, bool &take_modes) anope_override
data/anope-2.0.9/modules/pseudoclients/chanserv.cpp:468:65: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
void OnSetCorrectModes(User *user, Channel *chan, AccessGroup &access, bool &give_modes, bool &take_modes) anope_override
data/anope-2.0.9/modules/webcpanel/pages/chanserv/modes.cpp:42:37: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
replacements["MESSAGES"] = Anope::printf(CHAN_X_NOT_IN_USE, chname.c_str());
data/anope-2.0.9/modules/webcpanel/pages/nickserv/access.cpp:33:35: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
for (unsigned i = 0; i < na->nc->access.size(); ++i)
data/anope-2.0.9/modules/webcpanel/pages/nickserv/access.cpp:34:36: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
replacements["ACCESS"] = na->nc->access[i];
data/anope-2.0.9/modules/webcpanel/pages/nickserv/alist.cpp:42:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (access.empty())
data/anope-2.0.9/modules/webcpanel/pages/nickserv/alist.cpp:50:31: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
const ChanAccess *highest = access.Highest();
data/anope-2.0.9/src/access.cpp:231:14: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
ChanAccess *access;
data/anope-2.0.9/src/access.cpp:249:17: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
ci->AddAccess(access);
data/anope-2.0.9/src/access.cpp:250:9: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return access;
data/anope-2.0.9/src/access.cpp:348:44: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
FOREACH_RESULT(OnCheckPriv, MOD_RESULT, (access, name));
data/anope-2.0.9/src/channels.cpp:548:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, cmodes, args);
data/anope-2.0.9/src/channels.cpp:778:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, reason, args);
data/anope-2.0.9/src/command.cpp:103:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, sizeof(buf), translated_message, args);
data/anope-2.0.9/src/config.cpp:681:33: [4] (shell) popen:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
this->fp = (this->executable ? popen(this->name.c_str(), "r") : fopen((Anope::ConfigDir + "/" + this->name).c_str(), "r"));
data/anope-2.0.9/src/mail.cpp:30:15: [4] (shell) popen:
This causes a new program to execute and is difficult to use safely
(CWE-78). try using a library call that implements the same functionality
if available.
FILE *pipe = popen(sendmail_path.c_str(), "w");
data/anope-2.0.9/src/misc.cpp:363:44: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return Anope::string(buf) + " " + Anope::printf(Language::Translate(nc, _("(%s ago)")), Duration(Anope::CurTime - t, nc).c_str(), nc);
data/anope-2.0.9/src/misc.cpp:365:44: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
return Anope::string(buf) + " " + Anope::printf(Language::Translate(nc, _("(%s from now)")), Duration(t - Anope::CurTime, nc).c_str(), nc);
data/anope-2.0.9/src/misc.cpp:384:4: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(buf, sizeof(buf), Language::Translate(nc, days == 1 ? _("expires in %d day") : _("expires in %d days")), days);
data/anope-2.0.9/src/misc.cpp:391:5: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(buf, sizeof(buf), Language::Translate(nc, minutes == 1 ? _("expires in %d minute") : _("expires in %d minutes")), minutes);
data/anope-2.0.9/src/misc.cpp:398:5: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
snprintf(buf, sizeof(buf), Language::Translate(nc, hours == 1 && minutes == 1 ? _("expires in %d hour, %d minute") : (hours == 1 && minutes != 1 ? _("expires in %d hour, %d minutes") : (hours != 1 && minutes == 1 ? _("expires in %d hours, %d minute") : _("expires in %d hours, %d minutes")))), hours, minutes);
data/anope-2.0.9/src/misc.cpp:535:22: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
Anope::string Anope::printf(const char *fmt, ...)
data/anope-2.0.9/src/misc.cpp:540:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, sizeof(buf), fmt, args);
data/anope-2.0.9/src/nickcore.cpp:81:33: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
for (unsigned i = 0; i < this->access.size(); ++i)
data/anope-2.0.9/src/nickcore.cpp:82:27: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
data["access"] << this->access[i] << " ";
data/anope-2.0.9/src/nickcore.cpp:111:7: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
nc->access.clear();
data/anope-2.0.9/src/nickcore.cpp:113:8: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
nc->access.push_back(buf);
data/anope-2.0.9/src/nickcore.cpp:192:8: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
this->access.push_back(entry);
data/anope-2.0.9/src/nickcore.cpp:198:12: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (this->access.empty() || entry >= this->access.size())
data/anope-2.0.9/src/nickcore.cpp:198:45: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (this->access.empty() || entry >= this->access.size())
data/anope-2.0.9/src/nickcore.cpp:200:15: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return this->access[entry];
data/anope-2.0.9/src/nickcore.cpp:205:15: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
return this->access.size();
data/anope-2.0.9/src/nickcore.cpp:210:35: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
for (unsigned i = 0, end = this->access.size(); i < end; ++i)
data/anope-2.0.9/src/nickcore.cpp:211:13: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (this->access[i] == entry)
data/anope-2.0.9/src/nickcore.cpp:219:35: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
for (unsigned i = 0, end = this->access.size(); i < end; ++i)
data/anope-2.0.9/src/nickcore.cpp:220:13: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
if (this->access[i] == entry)
data/anope-2.0.9/src/nickcore.cpp:223:10: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
this->access.erase(this->access.begin() + i);
data/anope-2.0.9/src/nickcore.cpp:223:29: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
this->access.erase(this->access.begin() + i);
data/anope-2.0.9/src/nickcore.cpp:231:8: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
this->access.clear();
data/anope-2.0.9/src/nickcore.cpp:242:35: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
for (unsigned i = 0, end = this->access.size(); i < end; ++i)
data/anope-2.0.9/src/protocol.cpp:185:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:195:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:205:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:218:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:228:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:238:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:249:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:259:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:298:3: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:311:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:336:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/protocol.cpp:346:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, fmt, args);
data/anope-2.0.9/src/regchannel.cpp:99:2: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access("ChanAccess"), akick("AutoKick")
data/anope-2.0.9/src/regchannel.cpp:128:2: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
access("ChanAccess"), akick("AutoKick")
data/anope-2.0.9/src/regchannel.cpp:381:28: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
ChanAccess *acc = (*this->access)[index];
data/anope-2.0.9/src/serialize.cpp:31:48: [4] (race) access:
This usually indicates a security flaw. If an attacker can change anything
along the path between the call to access() and the file's actual use
(e.g., by moving files), the attacker can exploit the race condition
(CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
and try to open the file directly.
ci("ChannelInfo", ChannelInfo::Unserialize), access("ChanAccess", ChanAccess::Unserialize),
data/anope-2.0.9/src/socket_transport.cpp:84:12: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int len = vsnprintf(tbuffer, sizeof(tbuffer), message, vi);
data/anope-2.0.9/src/socket_transport.cpp:184:12: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
int len = vsnprintf(tbuffer, sizeof(tbuffer), message, vi);
data/anope-2.0.9/src/tools/anopesmtp.cpp:146:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, sizeof(buf), fmt, args);
data/anope-2.0.9/src/tools/anopesmtp.cpp:321:2: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(buf, smail.from.c_str());
data/anope-2.0.9/src/tools/anopesmtp.cpp:341:2: [4] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused).
strcat(buf, smail.to.c_str());
data/anope-2.0.9/src/users.cpp:328:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, translated_message, args);
data/anope-2.0.9/src/users.cpp:615:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, umodes, args);
data/anope-2.0.9/src/users.cpp:659:2: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
vsnprintf(buf, BUFSIZE - 1, umodes, args);
data/anope-2.0.9/src/win32/anope_windows.h:36:9: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
# undef snprintf
data/anope-2.0.9/src/win32/anope_windows.h:37:9: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
# undef vsnprintf
data/anope-2.0.9/src/win32/anope_windows.h:38:9: [4] (format) printf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
# undef printf
data/anope-2.0.9/src/win32/anope_windows.h:41:9: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define snprintf _snprintf
data/anope-2.0.9/src/win32/anope_windows.h:41:18: [4] (format) _snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define snprintf _snprintf
data/anope-2.0.9/src/win32/anope_windows.h:43:9: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define vsnprintf _vsnprintf
data/anope-2.0.9/src/init.cpp:517:2: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
srand(block->Get<unsigned>("seed") ^ time(NULL));
data/anope-2.0.9/src/win32/dl/dl.cpp:14:9: [3] (misc) LoadLibrary:
Ensure that the full path to the library is specified, or current directory
may be used (CWE-829, CWE-20). Use registry entry or GetWindowsDirectory to
find library path, if you aren't already.
return LoadLibrary(filename);
data/anope-2.0.9/src/win32/pthread/pthread.cpp:68:2: [3] (misc) InitializeCriticalSection:
Exceptions can be thrown in low-memory situations. Use
InitializeCriticalSectionAndSpinCount instead.
InitializeCriticalSection(mutex);
data/anope-2.0.9/src/win32/pthread/pthread.cpp:80:2: [3] (misc) EnterCriticalSection:
On some versions of Windows, exceptions can be thrown in low-memory
situations. Use InitializeCriticalSectionAndSpinCount instead.
EnterCriticalSection(mutex);
data/anope-2.0.9/src/win32/pthread/pthread.cpp:117:2: [3] (misc) EnterCriticalSection:
On some versions of Windows, exceptions can be thrown in low-memory
situations. Use InitializeCriticalSectionAndSpinCount instead.
EnterCriticalSection(mutex);
data/anope-2.0.9/include/anope.h:478:84: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
extern CoreExport uint64_t SipHash24(const void *src, unsigned long src_sz, const char key[16]);
data/anope-2.0.9/include/modules/httpd.h:57:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(this->buf, b, l);
data/anope-2.0.9/include/modules/os_news.h:23:8: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
const char *msgs[10];
data/anope-2.0.9/include/pstdint.h:765:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char str0[256], str1[256];
data/anope-2.0.9/include/pstdint.h:767:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (str0, "%d %x\n", 0, ~0);
data/anope-2.0.9/include/pstdint.h:769:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (str1, "%d %x\n", i8, ~0);
data/anope-2.0.9/include/pstdint.h:771:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (str1, "%u %x\n", u8, ~0);
data/anope-2.0.9/include/pstdint.h:773:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (str1, "%d %x\n", i16, ~0);
data/anope-2.0.9/include/pstdint.h:775:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (str1, "%u %x\n", u16, ~0);
data/anope-2.0.9/include/pstdint.h:777:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (str1, "%" PRINTF_INT32_MODIFIER "d %x\n", i32, ~0);
data/anope-2.0.9/include/pstdint.h:779:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (str1, "%" PRINTF_INT32_MODIFIER "u %x\n", u32, ~0);
data/anope-2.0.9/include/pstdint.h:782:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (str1, "%" PRINTF_INT64_MODIFIER "d %x\n", i64, ~0);
data/anope-2.0.9/include/pstdint.h:785:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (str1, "%" PRINTF_INTMAX_MODIFIER "d %x\n", imax, ~0);
data/anope-2.0.9/include/pstdint.h:787:2: [2] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf. Risk is low because the source has a constant maximum length.
sprintf (str1, "%" PRINTF_INTMAX_MODIFIER "u %x\n", umax, ~0);
data/anope-2.0.9/include/version.cpp:23:5: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd.open((git_dir + "/HEAD").c_str(), std::ios::in);
data/anope-2.0.9/include/version.cpp:35:5: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd.open((git_dir + "/" + filebuf).c_str(), std::ios::in);
data/anope-2.0.9/include/version.cpp:89:18: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
int ibuild = atoi(filebuf.substr(tab + 1).c_str()) + 1;
data/anope-2.0.9/include/version.cpp:101:5: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fd.open(buildh.c_str(), std::ios::out);
data/anope-2.0.9/modules/commands/bs_kick.cpp:1077:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/anope-2.0.9/modules/commands/os_logsearch.cpp:20:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char timestamp[32];
data/anope-2.0.9/modules/database/db_flatfile.cpp:202:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[512];
data/anope-2.0.9/modules/database/db_old.cpp:171:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char input[3];
data/anope-2.0.9/modules/database/db_old.cpp:314:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char filename[1024]; /* Name of the database file */
data/anope-2.0.9/modules/database/db_old.cpp:326:7: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
fp = fopen(f->filename, "rb");
data/anope-2.0.9/modules/database/db_old.cpp:455:4: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char pwbuf[32];
data/anope-2.0.9/modules/database/db_old.cpp:587:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char sbuf[32];
data/anope-2.0.9/modules/database/db_old.cpp:749:4: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char namebuf[64];
data/anope-2.0.9/modules/database/db_old.cpp:764:4: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char pwbuf[32];
data/anope-2.0.9/modules/database/db_old.cpp:954:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char sbuf[32];
data/anope-2.0.9/modules/database/db_old.cpp:1224:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char who[32];
data/anope-2.0.9/modules/database/db_old.cpp:1285:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char who[32];
data/anope-2.0.9/modules/encryption/enc_bcrypt.cpp:365:17: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static unsigned char BF_itoa64[64 + 1] =
data/anope-2.0.9/modules/encryption/enc_bcrypt.cpp:368:17: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static unsigned char BF_atoi64[0x60] = {
data/anope-2.0.9/modules/encryption/enc_bcrypt.cpp:641:23: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static const unsigned char flags_by_subtype[26] =
data/anope-2.0.9/modules/encryption/enc_bcrypt.cpp:758:2: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(output, setting, 7 + 22 - 1);
data/anope-2.0.9/modules/encryption/enc_bcrypt.cpp:851:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char entropy[16];
data/anope-2.0.9/modules/encryption/enc_bcrypt.cpp:855:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char salt[32];
data/anope-2.0.9/modules/encryption/enc_bcrypt.cpp:863:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char hash[64];
data/anope-2.0.9/modules/encryption/enc_md5.cpp:39:17: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static unsigned char PADDING[64] = {
data/anope-2.0.9/modules/encryption/enc_md5.cpp:93:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char buffer[64]; /* input buffer */
data/anope-2.0.9/modules/encryption/enc_md5.cpp:94:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char digest[16]; /* final digest */
data/anope-2.0.9/modules/encryption/enc_md5.cpp:120:32: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
void Transform(const unsigned char block[64])
data/anope-2.0.9/modules/encryption/enc_md5.cpp:270:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&this->buffer[index], input, partLen);
data/anope-2.0.9/modules/encryption/enc_md5.cpp:282:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&this->buffer[index], &input[i], len - i);
data/anope-2.0.9/modules/encryption/enc_md5.cpp:290:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char bits[8];
data/anope-2.0.9/modules/encryption/enc_old.cpp:65:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char digest[32], digest2[16];
data/anope-2.0.9/modules/encryption/enc_old.cpp:69:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(digest, hash.first, hash.second);
data/anope-2.0.9/modules/encryption/enc_sha1.cpp:27:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char c[64];
data/anope-2.0.9/modules/encryption/enc_sha1.cpp:61:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char buffer[64];
data/anope-2.0.9/modules/encryption/enc_sha1.cpp:62:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char digest[20];
data/anope-2.0.9/modules/encryption/enc_sha1.cpp:64:32: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
void Transform(const unsigned char buf[64])
data/anope-2.0.9/modules/encryption/enc_sha1.cpp:69:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(block.c, buf, 64);
data/anope-2.0.9/modules/encryption/enc_sha1.cpp:138:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&this->buffer[j], data, (i = 64 - j));
data/anope-2.0.9/modules/encryption/enc_sha1.cpp:146:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&this->buffer[j], &data[i], len - i);
data/anope-2.0.9/modules/encryption/enc_sha1.cpp:152:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char finalcount[8];
data/anope-2.0.9/modules/encryption/enc_sha256.cpp:152:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char block[2 * SHA256_BLOCK_SIZE];
data/anope-2.0.9/modules/encryption/enc_sha256.cpp:154:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char digest[SHA256_DIGEST_SIZE];
data/anope-2.0.9/modules/encryption/enc_sha256.cpp:180:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&this->block[this->len], message, rem_len);
data/anope-2.0.9/modules/encryption/enc_sha256.cpp:188:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(shifted_message, message + rem_len, mlen - rem_len);
data/anope-2.0.9/modules/encryption/enc_sha256.cpp:192:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(this->block, &shifted_message[block_nb << 6], rem_len);
data/anope-2.0.9/modules/encryption/enc_sha256.cpp:256:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[33];
data/anope-2.0.9/modules/encryption/enc_sha256.cpp:269:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf2[33];
data/anope-2.0.9/modules/extra/m_regex_posix.cpp:23:4: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE];
data/anope-2.0.9/modules/extra/m_regex_tre.cpp:24:4: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE];
data/anope-2.0.9/modules/m_dns.cpp:46:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], token.c_str(), token.length());
data/anope-2.0.9/modules/m_dns.cpp:318:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &s, 2);
data/anope-2.0.9/modules/m_dns.cpp:322:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &s, 2);
data/anope-2.0.9/modules/m_dns.cpp:338:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &s, 2);
data/anope-2.0.9/modules/m_dns.cpp:342:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &s, 2);
data/anope-2.0.9/modules/m_dns.cpp:346:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &l, 4);
data/anope-2.0.9/modules/m_dns.cpp:361:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &s, 2);
data/anope-2.0.9/modules/m_dns.cpp:364:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &a.sa4.sin_addr, 4);
data/anope-2.0.9/modules/m_dns.cpp:378:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &s, 2);
data/anope-2.0.9/modules/m_dns.cpp:381:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &a.sa6.sin6_addr, 16);
data/anope-2.0.9/modules/m_dns.cpp:398:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[packet_pos_save], &s, 2);
data/anope-2.0.9/modules/m_dns.cpp:418:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &l, 4);
data/anope-2.0.9/modules/m_dns.cpp:422:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &l, 4);
data/anope-2.0.9/modules/m_dns.cpp:426:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &l, 4);
data/anope-2.0.9/modules/m_dns.cpp:430:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &l, 4);
data/anope-2.0.9/modules/m_dns.cpp:434:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[pos], &l, 4);
data/anope-2.0.9/modules/m_dns.cpp:438:7: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&output[packet_pos_save], &s, 2);
data/anope-2.0.9/modules/m_dns.cpp:472:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char packet_buffer[524];
data/anope-2.0.9/modules/m_dns.cpp:526:15: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char buffer[65535];
data/anope-2.0.9/modules/m_dns.cpp:530:6: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buffer, &s, 2);
data/anope-2.0.9/modules/m_dns.cpp:581:12: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char packet_buffer[524];
data/anope-2.0.9/modules/m_dns.cpp:597:14: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char buffer[524];
data/anope-2.0.9/modules/m_dns.cpp:634:13: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char buffer[524];
data/anope-2.0.9/modules/m_httpd.cpp:15:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char timebuf[64];
data/anope-2.0.9/modules/m_proxyscan.cpp:152:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[4 + sizeof(target_addr.sa4.sin_addr.s_addr) + sizeof(target_addr.sa4.sin_port)];
data/anope-2.0.9/modules/m_proxyscan.cpp:168:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buf + ptr, &target_addr.sa4.sin_addr.s_addr, sizeof(target_addr.sa4.sin_addr.s_addr));
data/anope-2.0.9/modules/m_proxyscan.cpp:170:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(buf + ptr, &target_addr.sa4.sin_port, sizeof(target_addr.sa4.sin_port));
data/anope-2.0.9/modules/webcpanel/static_fileserver.cpp:22:11: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
int fd = open((template_base + "/" + this->file_name).c_str(), O_RDONLY);
data/anope-2.0.9/modules/webcpanel/static_fileserver.cpp:35:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[BUFSIZE];
data/anope-2.0.9/modules/webcpanel/template_fileserver.cpp:95:11: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
int fd = open((template_base + "/" + this->file_name).c_str(), O_RDONLY);
data/anope-2.0.9/modules/webcpanel/template_fileserver.cpp:107:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[BUFSIZE];
data/anope-2.0.9/src/base64.cpp:84:11: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
unsigned char input[3] = { '\0', '\0', '\0' };
data/anope-2.0.9/src/channels.cpp:543:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/channels.cpp:776:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/command.cpp:98:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[4096]; // Messages can be really big.
data/anope-2.0.9/src/config.cpp:681:66: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
this->fp = (this->executable ? popen(this->name.c_str(), "r") : fopen((Anope::ConfigDir + "/" + this->name).c_str(), "r"));
data/anope-2.0.9/src/config.cpp:705:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE];
data/anope-2.0.9/src/hashcomp.cpp:16:17: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
static unsigned char case_map_upper[256], case_map_lower[256];
data/anope-2.0.9/src/init.cpp:217:18: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
FILE *pidfile = fopen(Config->GetBlock("serverinfo")->Get<const Anope::string>("pid").c_str(), "w");
data/anope-2.0.9/src/logger.cpp:31:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tbuf[256];
data/anope-2.0.9/src/logger.cpp:56:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char timestamp[32];
data/anope-2.0.9/src/main.cpp:79:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[PATH_MAX];
data/anope-2.0.9/src/messages.cpp:243:12: [2] (misc) fopen:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
FILE *f = fopen(Config->GetBlock("serverinfo")->Get<const Anope::string>("motd").c_str(), "r");
data/anope-2.0.9/src/messages.cpp:247:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE];
data/anope-2.0.9/src/messages.cpp:463:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[64];
data/anope-2.0.9/src/misc.cpp:358:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE];
data/anope-2.0.9/src/misc.cpp:378:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[256];
data/anope-2.0.9/src/misc.cpp:538:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/anope-2.0.9/src/misc.cpp:593:2: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(dest, d.c_str(), std::min(d.length() + 1, sz));
data/anope-2.0.9/src/misc.cpp:610:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char errbuf[513];
data/anope-2.0.9/src/misc.cpp:742:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(static_cast<void*>(&addr), addrresult->ai_addr, addrresult->ai_addrlen);
data/anope-2.0.9/src/modulemanager.cpp:77:18: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
int target_fd = mkstemp(tmp_output);
data/anope-2.0.9/src/modulemanager.cpp:97:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buffer[1024];
data/anope-2.0.9/src/nickcore.cpp:302:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char key[16];
data/anope-2.0.9/src/pipeengine.cpp:53:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char dummy[512];
data/anope-2.0.9/src/protocol.cpp:183:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:193:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:203:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:216:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:226:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:236:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:247:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:257:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:296:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:309:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:334:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/protocol.cpp:344:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/siphash.cpp:98:72: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
uint64_t Anope::SipHash24(const void *src, unsigned long src_sz, const char key[16])
data/anope-2.0.9/src/socket_transport.cpp:26:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tbuffer[NET_BUFSIZE];
data/anope-2.0.9/src/socket_transport.cpp:78:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tbuffer[BUFSIZE];
data/anope-2.0.9/src/socket_transport.cpp:109:2: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(this->buf, b, l);
data/anope-2.0.9/src/socket_transport.cpp:128:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tbuffer[NET_BUFSIZE];
data/anope-2.0.9/src/socket_transport.cpp:178:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tbuffer[BUFSIZE];
data/anope-2.0.9/src/sockets.cpp:79:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char address[INET6_ADDRSTRLEN];
data/anope-2.0.9/src/sockets.cpp:100:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char address[128];
data/anope-2.0.9/src/sockets.cpp:197:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[INET6_ADDRSTRLEN];
data/anope-2.0.9/src/tools/anopesmtp.cpp:97:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char timestamp[32];
data/anope-2.0.9/src/tools/anopesmtp.cpp:113:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tbuf[256];
data/anope-2.0.9/src/tools/anopesmtp.cpp:132:7: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
file.open(get_logname().c_str(), std::ios_base::out | std::ios_base::app);
data/anope-2.0.9/src/tools/anopesmtp.cpp:143:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[256];
data/anope-2.0.9/src/tools/anopesmtp.cpp:233:3: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&addr.sin_addr, hent->h_addr, hent->h_length);
data/anope-2.0.9/src/tools/anopesmtp.cpp:281:9: [2] (integer) atol:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
return atol(text.substr(0, tmp).c_str());
data/anope-2.0.9/src/tools/anopesmtp.cpp:287:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/anope-2.0.9/src/tools/anopesmtp.cpp:320:2: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buf, "MAIL FROM: <");
data/anope-2.0.9/src/tools/anopesmtp.cpp:322:2: [2] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant string.
strcat(buf, ">\r\n");
data/anope-2.0.9/src/tools/anopesmtp.cpp:340:2: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(buf, "RCPT TO: <");
data/anope-2.0.9/src/tools/anopesmtp.cpp:342:2: [2] (buffer) strcat:
Does not check for buffer overflows when concatenating to destination
[MS-banned] (CWE-120). Consider using strcat_s, strncat, strlcat, or
snprintf (warning: strncat is easily misused). Risk is low because the
source is a constant string.
strcat(buf, ">\r\n");
data/anope-2.0.9/src/tools/anopesmtp.cpp:432:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[1024];
data/anope-2.0.9/src/tools/anopesmtp.cpp:469:10: [2] (integer) atoi:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
port = atoi(aport);
data/anope-2.0.9/src/tools/anopesmtp.cpp:489:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[8192];
data/anope-2.0.9/src/users.cpp:323:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/users.cpp:610:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/users.cpp:654:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[BUFSIZE] = "";
data/anope-2.0.9/src/win32/anope_windows.h:77:12: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
extern int mkstemp(char *input);
data/anope-2.0.9/src/win32/dir/dir.cpp:14:2: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char real_path[MAX_PATH];
data/anope-2.0.9/src/win32/socket.cpp:81:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(dst, &sin->sin_addr, sizeof(in_addr));
data/anope-2.0.9/src/win32/socket.cpp:84:5: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(dst, &sin6->sin6_addr, sizeof(in6_addr));
data/anope-2.0.9/src/win32/socket.cpp:115:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&sin->sin_addr, src, sizeof(in_addr));
data/anope-2.0.9/src/win32/socket.cpp:120:4: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
memcpy(&sin6->sin6_addr, src, sizeof(in6_addr));
data/anope-2.0.9/src/win32/windows.cpp:243:5: [2] (tmpfile) mkstemp:
Potential for temporary file vulnerability in some circumstances. Some
older Unix-like systems create temp files with permission to write by all
by default, so be sure to set the umask to override this. Also, some older
Unix systems might fail to use O_EXCL when opening the file, so make sure
that O_EXCL is used by the library (CWE-377).
int mkstemp(char *input)
data/anope-2.0.9/src/win32/windows.cpp:252:11: [2] (misc) open:
Check when opening files - can an attacker redirect it (via symlinks),
force the opening of special file type (e.g., device files), move things
around to create a race condition, control its ancestors, or change its
contents? (CWE-362).
int fd = open(input, O_WRONLY | O_CREAT, S_IREAD | S_IWRITE);
data/anope-2.0.9/modules/database/db_flatfile.cpp:45:7: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
bool read;
data/anope-2.0.9/modules/database/db_flatfile.cpp:47:32: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
LoadData() : fs(NULL), id(0), read(false) { }
data/anope-2.0.9/modules/database/db_flatfile.cpp:51:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (!read)
data/anope-2.0.9/modules/database/db_old.cpp:31:21: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#define getc_db(f) (fgetc((f)->fp))
data/anope-2.0.9/modules/database/db_old.cpp:334:14: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
myversion = fgetc(fp) << 24 | fgetc(fp) << 16 | fgetc(fp) << 8 | fgetc(fp);
data/anope-2.0.9/modules/database/db_old.cpp:334:32: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
myversion = fgetc(fp) << 24 | fgetc(fp) << 16 | fgetc(fp) << 8 | fgetc(fp);
data/anope-2.0.9/modules/database/db_old.cpp:334:50: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
myversion = fgetc(fp) << 24 | fgetc(fp) << 16 | fgetc(fp) << 8 | fgetc(fp);
data/anope-2.0.9/modules/database/db_old.cpp:334:67: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
myversion = fgetc(fp) << 24 | fgetc(fp) << 16 | fgetc(fp) << 8 | fgetc(fp);
data/anope-2.0.9/modules/database/db_old.cpp:362:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c1 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:363:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c2 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:376:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c1 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:377:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c2 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:410:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c1 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:411:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c2 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:412:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c3 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:413:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c4 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:426:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c1 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:427:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c2 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:428:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c3 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:429:7: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
c4 = fgetc(f->fp);
data/anope-2.0.9/modules/database/db_old.cpp:464:27: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
nc->pass = Hex(pwbuf, strlen(pwbuf));
data/anope-2.0.9/modules/m_redis.cpp:119:9: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
sz = strlen(buf);
data/anope-2.0.9/modules/webcpanel/static_fileserver.cpp:36:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while ((i = read(fd, buffer, sizeof(buffer))) > 0)
data/anope-2.0.9/modules/webcpanel/template_fileserver.cpp:108:14: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while ((i = read(fd, buffer, sizeof(buffer) - 1)) > 0)
data/anope-2.0.9/src/init.cpp:291:2: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
umask(DEFUMASK);
data/anope-2.0.9/src/logger.cpp:44:14: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
s = tbuf + strlen(tbuf);
data/anope-2.0.9/src/messages.cpp:250:8: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
buf[strlen(buf) - 1] = 0;
data/anope-2.0.9/src/modulemanager.cpp:100:10: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
source.read(buffer, std::min(want, static_cast<int>(sizeof(buffer))));
data/anope-2.0.9/src/pipeengine.cpp:54:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while (read(this->GetFD(), dummy, 512) == 512);
data/anope-2.0.9/src/pipeengine.cpp:65:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
return read(this->GetFD(), data, sz);
data/anope-2.0.9/src/tools/anopesmtp.cpp:76:36: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#define ano_sockread(fd, buf, len) read(fd, buf, len)
data/anope-2.0.9/src/tools/anopesmtp.cpp:249:47: [1] (buffer) strlen:
Does not handle strings that are not \0-terminated; if given one it may
perform an over-read (it could cause a crash if unprotected) (CWE-126).
int result = ano_sockwrite(smail.sock, text, strlen(text));
data/anope-2.0.9/src/win32/socket.cpp:19:5: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
int read(int fd, char *buf, size_t count)
data/anope-2.0.9/src/win32/socket.h:9:9: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#define read read_not_used
data/anope-2.0.9/src/win32/socket.h:12:8: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#undef read
data/anope-2.0.9/src/win32/socket.h:20:23: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
extern CoreExport int read(int fd, char *buf, size_t count);
ANALYSIS SUMMARY:
Hits = 357
Lines analyzed = 86114 in approximately 2.26 seconds (38141 lines/second)
Physical Source Lines of Code (SLOC) = 64371
Hits@level = [0] 51 [1] 36 [2] 165 [3] 5 [4] 150 [5] 1
Hits@level+ = [0+] 408 [1+] 357 [2+] 321 [3+] 156 [4+] 151 [5+] 1
Hits/KSLOC@level+ = [0+] 6.33826 [1+] 5.54598 [2+] 4.98672 [3+] 2.42345 [4+] 2.34578 [5+] 0.0155349
Dot directories skipped = 2 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.