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/muparser-2.2.6.1+dfsg/include/muParser.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserBase.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserBytecode.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserCallback.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserDLL.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserDef.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserError.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserFixes.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserInt.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserStack.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserTemplateMagic.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserTest.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserToken.h
Examining data/muparser-2.2.6.1+dfsg/include/muParserTokenReader.h
Examining data/muparser-2.2.6.1+dfsg/samples/example1/example1.cpp
Examining data/muparser-2.2.6.1+dfsg/samples/example2/example2.c
Examining data/muparser-2.2.6.1+dfsg/src/muParser.cpp
Examining data/muparser-2.2.6.1+dfsg/src/muParserBase.cpp
Examining data/muparser-2.2.6.1+dfsg/src/muParserBytecode.cpp
Examining data/muparser-2.2.6.1+dfsg/src/muParserCallback.cpp
Examining data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp
Examining data/muparser-2.2.6.1+dfsg/src/muParserError.cpp
Examining data/muparser-2.2.6.1+dfsg/src/muParserInt.cpp
Examining data/muparser-2.2.6.1+dfsg/src/muParserTest.cpp
Examining data/muparser-2.2.6.1+dfsg/src/muParserTokenReader.cpp
FINAL RESULTS:
data/muparser-2.2.6.1+dfsg/samples/example2/example2.c:14: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.
#define myprintf printf
data/muparser-2.2.6.1+dfsg/samples/example2/example2.c:20:22: [4] (format) wprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
#define myprintf wprintf
data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp:195:5: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(s_tmpOutBuf, "%s", p->GetVersion().c_str());
data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp:673:5: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(s_tmpOutBuf, "%s", p->GetExpr().c_str());
data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp:1036:5: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(s_tmpOutBuf, "%s", pMsg);
data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp:1055:5: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(s_tmpOutBuf, "%s", pToken);
data/muparser-2.2.6.1+dfsg/src/muParserBase.cpp:1763:19: [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 *pFile = fopen("bulk_dbg.txt", "w");
data/muparser-2.2.6.1+dfsg/samples/example2/example2.c:15:22: [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).
#define mystrlen strlen
data/muparser-2.2.6.1+dfsg/samples/example2/example2.c:21:22: [1] (buffer) wcslen:
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).
#define mystrlen wcslen
data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp:793:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(szName, item->first.c_str(), sizeof(szName));
data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp:795:5: [1] (buffer) wcsncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
wcsncpy(szName, item->first.c_str(), sizeof(szName));
data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp:870:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(szName, item->first.c_str(), sizeof(szName));
data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp:872:5: [1] (buffer) wcsncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
wcsncpy(szName, item->first.c_str(), sizeof(szName));
data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp:969:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(szName, item->first.c_str(), sizeof(szName));
data/muparser-2.2.6.1+dfsg/src/muParserDLL.cpp:971:5: [1] (buffer) wcsncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
wcsncpy(szName, item->first.c_str(), sizeof(szName));
data/muparser-2.2.6.1+dfsg/src/muParserTest.cpp:1552:15: [1] (buffer) getchar:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
while (!getchar());
ANALYSIS SUMMARY:
Hits = 16
Lines analyzed = 11199 in approximately 0.32 seconds (35510 lines/second)
Physical Source Lines of Code (SLOC) = 6932
Hits@level = [0] 2 [1] 9 [2] 1 [3] 0 [4] 6 [5] 0
Hits@level+ = [0+] 18 [1+] 16 [2+] 7 [3+] 6 [4+] 6 [5+] 0
Hits/KSLOC@level+ = [0+] 2.59665 [1+] 2.30814 [2+] 1.00981 [3+] 0.865551 [4+] 0.865551 [5+] 0
Dot directories skipped = 1 (--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.