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/filter-2.6.3+ds1/actions.c
Examining data/filter-2.6.3+ds1/audit.h
Examining data/filter-2.6.3+ds1/buffer.c
Examining data/filter-2.6.3+ds1/defs.h
Examining data/filter-2.6.3+ds1/filter.h
Examining data/filter-2.6.3+ds1/lock.c
Examining data/filter-2.6.3+ds1/lock.h
Examining data/filter-2.6.3+ds1/mcprt.h
Examining data/filter-2.6.3+ds1/mk_lockname.c
Examining data/filter-2.6.3+ds1/nl_types.h
Examining data/filter-2.6.3+ds1/parse.c
Examining data/filter-2.6.3+ds1/regexp.c
Examining data/filter-2.6.3+ds1/regexp.h
Examining data/filter-2.6.3+ds1/rules.c
Examining data/filter-2.6.3+ds1/s_filter.h
Examining data/filter-2.6.3+ds1/summarize.c
Examining data/filter-2.6.3+ds1/utils.c
Examining data/filter-2.6.3+ds1/utils.h
Examining data/filter-2.6.3+ds1/version.h
Examining data/filter-2.6.3+ds1/sysdefs.h
Examining data/filter-2.6.3+ds1/config.h
Examining data/filter-2.6.3+ds1/filter.c
Examining data/filter-2.6.3+ds1/audit.c
Examining data/filter-2.6.3+ds1/strtokq.c
Examining data/filter-2.6.3+ds1/istrcmp.c
FINAL RESULTS:
data/filter-2.6.3+ds1/lock.c:366:2: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(dotlock_name, username, SLEN);
data/filter-2.6.3+ds1/parse.c:395:5: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(cond_argument, word, SLEN);
data/filter-2.6.3+ds1/parse.c:397:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(cond_argument, "/", SLEN);
data/filter-2.6.3+ds1/rules.c:334:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,
data/filter-2.6.3+ds1/rules.c:341:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, "\"", SLEN);
data/filter-2.6.3+ds1/rules.c:342:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, sender, SLEN);
data/filter-2.6.3+ds1/rules.c:343:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, "\"", SLEN);
data/filter-2.6.3+ds1/rules.c:350:8: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:355:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, Hfrom, SLEN);
data/filter-2.6.3+ds1/rules.c:361:8: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:365:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, "\"", SLEN);
data/filter-2.6.3+ds1/rules.c:366:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, subject, SLEN);
data/filter-2.6.3+ds1/rules.c:367:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, "\"", SLEN);
data/filter-2.6.3+ds1/rules.c:374:8: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:379:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, "\"", SLEN);
data/filter-2.6.3+ds1/rules.c:381:9: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, "Re: ", SLEN);
data/filter-2.6.3+ds1/rules.c:382:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, subject, SLEN);
data/filter-2.6.3+ds1/rules.c:383:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, "\"", SLEN);
data/filter-2.6.3+ds1/rules.c:390:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:394:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, itoa(timerec->tm_mday,FALSE), SLEN);
data/filter-2.6.3+ds1/rules.c:400:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:404:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, itoa(timerec->tm_wday,FALSE), SLEN);
data/filter-2.6.3+ds1/rules.c:410:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:420:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:424:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, itoa(timerec->tm_year,TRUE), SLEN);
data/filter-2.6.3+ds1/rules.c:430:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:435:6: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, itoa(fullyear,FALSE), SLEN);
data/filter-2.6.3+ds1/rules.c:442:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:446:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, itoa(timerec->tm_hour,FALSE), SLEN);
data/filter-2.6.3+ds1/rules.c:452:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:456:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, itoa(timerec->tm_hour,FALSE), SLEN);
data/filter-2.6.3+ds1/rules.c:457:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, ":", SLEN);
data/filter-2.6.3+ds1/rules.c:458:7: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer, itoa(timerec->tm_min,TRUE), SLEN);
data/filter-2.6.3+ds1/rules.c:471:5: [5] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings. Risk is high; the length parameter
appears to be a constant, instead of computing the number of characters
left.
strncat(buffer,
data/filter-2.6.3+ds1/actions.c:109:8: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(buffer, "%s %s %s", sendmail, smflags, address);
data/filter-2.6.3+ds1/actions.c:111:8: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(buffer, "%s %s", mailer, address);
data/filter-2.6.3+ds1/actions.c:114:16: [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.
if ((pipefd = popen(buffer, "w")) == NULL) {
data/filter-2.6.3+ds1/actions.c:117:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/actions.c:125:3: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(buffer, "(%s %s %s < %s ) &",
data/filter-2.6.3+ds1/actions.c:127:8: [4] (shell) system:
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.
exit(system(buffer));
data/filter-2.6.3+ds1/actions.c:154:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(pipefd,
data/filter-2.6.3+ds1/actions.c:160:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(pipefd,
data/filter-2.6.3+ds1/actions.c:166:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(pipefd,
data/filter-2.6.3+ds1/actions.c:181:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(pipefd,
data/filter-2.6.3+ds1/actions.c:225:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/actions.c:235:12: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/actions.c:258:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/actions.c:278:7: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/actions.c:295:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr, catgets(elm_msg_cat,FilterSet,
data/filter-2.6.3+ds1/actions.c:299:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr, catgets(elm_msg_cat,FilterSet,
data/filter-2.6.3+ds1/actions.c:309:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/actions.c:366:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr, catgets(elm_msg_cat,FilterSet,FilterSavedMessage,
data/filter-2.6.3+ds1/actions.c:400:7: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/actions.c:448:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr, catgets(elm_msg_cat,FilterSet,
data/filter-2.6.3+ds1/actions.c:452:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr, catgets(elm_msg_cat,FilterSet,
data/filter-2.6.3+ds1/actions.c:463:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/actions.c:515:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr, catgets(elm_msg_cat,FilterSet,FilterExecutingCmd,
data/filter-2.6.3+ds1/actions.c:522:2: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(buffer, "%s",command);
data/filter-2.6.3+ds1/actions.c:530:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/actions.c:551:8: [4] (shell) system:
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.
exit(system(buffer));
data/filter-2.6.3+ds1/actions.c:555:9: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/actions.c:576:2: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(mailbox, "%s/%s", home, EMERGENCY_MAILBOX);
data/filter-2.6.3+ds1/actions.c:580:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr, catgets(elm_msg_cat,FilterSet,FilterCantOpenEither,
data/filter-2.6.3+ds1/actions.c:584:4: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(mailbox,"%s/%s", home, EMERG_MBOX);
data/filter-2.6.3+ds1/actions.c:589:5: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr, catgets(elm_msg_cat,FilterSet,
data/filter-2.6.3+ds1/actions.c:593:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterCantOpenAny,
data/filter-2.6.3+ds1/actions.c:604:9: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,
data/filter-2.6.3+ds1/actions.c:611:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,
data/filter-2.6.3+ds1/audit.c:62:5: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(stuff, "%s %s", date, username);
data/filter-2.6.3+ds1/defs.h:236:14: [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.
extern FILE *popen(const char *, const char *);
data/filter-2.6.3+ds1/defs.h:314:10: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf x ; \
data/filter-2.6.3+ds1/defs.h:426:18: [4] (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).
char *strtok(), *strcpy(), *strcat(), *strncpy(); /* more in string.h in ANSI */
data/filter-2.6.3+ds1/defs.h:426:29: [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).
char *strtok(), *strcpy(), *strcat(), *strncpy(); /* more in string.h in ANSI */
data/filter-2.6.3+ds1/defs.h:456:18: [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 MCprintf printf
data/filter-2.6.3+ds1/defs.h:457:19: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
#define MCfprintf fprintf
data/filter-2.6.3+ds1/defs.h:458:19: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
#define MCsprintf sprintf
data/filter-2.6.3+ds1/filter.c:122:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stderr, catgets(elm_msg_cat,FilterSet,FilterUsage,
data/filter-2.6.3+ds1/filter.c:261:3: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(user_mailbox, "%s", mailhome);
data/filter-2.6.3+ds1/filter.c:265:4: [4] (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).
strcpy(user_mailbox, tmpstr);
data/filter-2.6.3+ds1/filter.c:268:4: [4] (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).
strcpy(user_mailbox, overridemailbox);
data/filter-2.6.3+ds1/filter.c:289:4: [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(buffer,firstletter);
data/filter-2.6.3+ds1/filter.c:290:4: [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(buffer,tmpstr+2);
data/filter-2.6.3+ds1/filter.c:307:4: [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(buffer,username);
data/filter-2.6.3+ds1/filter.c:308:4: [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(buffer,tmpstr+2);
data/filter-2.6.3+ds1/filter.c:314:2: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(filterlog,"%s/.filter/%s",home,FILTERLOG);
data/filter-2.6.3+ds1/filter.c:315:2: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(filtersum,"%s/.filter/%s",home,FILTERSUM);
data/filter-2.6.3+ds1/filter.c:319:7: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(filterfile,"%s/.filter/%s",home,FILTERFILE);
data/filter-2.6.3+ds1/filter.c:330:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(stderr,
data/filter-2.6.3+ds1/filter.c:350:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterCouldntGetRules,
data/filter-2.6.3+ds1/filter.c:362:3: [4] (format) sprintf:
Potential format string problem (CWE-134). Make format string constant.
sprintf(buffer,
data/filter-2.6.3+ds1/filter.c:446:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/filter.h:303:7: [4] (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).
char *strcpy(), *strcat();
data/filter-2.6.3+ds1/filter.h:303:18: [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).
char *strcpy(), *strcat();
data/filter-2.6.3+ds1/filter.h:307:9: [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 *popen();
data/filter-2.6.3+ds1/lock.c:208:5: [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(fname, F_OK) != 0)
data/filter-2.6.3+ds1/lock.c:305:2: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(lockfilename,"%s.lock", foldername);
data/filter-2.6.3+ds1/lock.c:337:2: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(lockfilename,"%s.lock", foldername);
data/filter-2.6.3+ds1/lock.c:359:3: [4] (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).
strcpy(maildir, mailhome);
data/filter-2.6.3+ds1/lock.c:371:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/lock.c:390:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/lock.c:403:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/mk_lockname.c:49:9: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(lock_name, "%s.lock", file_to_lock);
data/filter-2.6.3+ds1/parse.c:137:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/parse.c:182:5: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterCouldntReadRules,
data/filter-2.6.3+ds1/parse.c:198:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/parse.c:277:14: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/parse.c:304:12: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/parse.c:323:14: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/parse.c:373:5: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/parse.c:431:12: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/parse.c:450:14: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/parse.c:492:12: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:160:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/rules.c:246:44: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case CONTAINS: if (outfptr != NULL) fprintf(outfptr,
data/filter-2.6.3+ds1/rules.c:489:40: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
default : if (outfptr != NULL) fprintf(outfptr,
data/filter-2.6.3+ds1/rules.c:532:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterAlways,
data/filter-2.6.3+ds1/rules.c:538:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterRuleIf,
data/filter-2.6.3+ds1/rules.c:545:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterNot,
data/filter-2.6.3+ds1/rules.c:563:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/rules.c:568:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterThen,
data/filter-2.6.3+ds1/summarize.c:89:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:100:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:120:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:139:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterSumTitle,
data/filter-2.6.3+ds1/summarize.c:144:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/summarize.c:156:3: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/summarize.c:170:5: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterDefaultRuleMesg,
data/filter-2.6.3+ds1/summarize.c:173:5: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/summarize.c:188:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterRuleNum,
data/filter-2.6.3+ds1/summarize.c:191:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case BOUNCE: fprintf(outfptr,
data/filter-2.6.3+ds1/summarize.c:196:21: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case LEAVE: fprintf(outfptr,
data/filter-2.6.3+ds1/summarize.c:201:23: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case DELETE_MSG: fprintf(outfptr,
data/filter-2.6.3+ds1/summarize.c:206:23: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case SAVE : fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:212:23: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case SAVECC: fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:218:23: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case FORWARD: fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:224:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case RESEND: fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:230:23: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case FORWARDC: fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:236:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case EXEC : fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:242:23: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case EXECC : fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:249:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,
data/filter-2.6.3+ds1/summarize.c:266:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/summarize.c:272:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,FilterSet,FilterExplicitLog,
data/filter-2.6.3+ds1/utils.c:108:8: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:122:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:134:2: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(fptr,catgets(elm_msg_cat,FilterSet,FilterMailFrom,
data/filter-2.6.3+ds1/utils.c:143:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(fptr,catgets(elm_msg_cat,FilterSet,FilterAbout,
data/filter-2.6.3+ds1/utils.c:149:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(fptr,catgets(elm_msg_cat,FilterSet,FilterAddressedTo,
data/filter-2.6.3+ds1/utils.c:155:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case DELETE_MSG : fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:159:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case FAILED_SAVE: fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:164:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case SAVE : fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:169:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case SAVECC : fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:174:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case FORWARD : fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:179:23: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case FORWARDC : fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:185:18: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case RESEND : fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:190:18: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case BOUNCE : fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:195:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case EXEC : fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:200:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case EXECC : fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:205:22: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
case LEAVE : fprintf(fptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:212:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(fptr,catgets(elm_msg_cat,FilterSet,FilterByRule,
data/filter-2.6.3+ds1/utils.c:215:4: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(fptr,catgets(elm_msg_cat,FilterSet,FilterTheDefaultAction,
data/filter-2.6.3+ds1/utils.c:229:6: [4] (format) fprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
fprintf(outfptr,catgets(elm_msg_cat,
data/filter-2.6.3+ds1/utils.c:334:6: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(filename, "%s%s%s",
data/filter-2.6.3+ds1/utils.c:367:2: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(tmpfilename,"%s_%s.%d", filter_temp, username, mypid);
data/filter-2.6.3+ds1/utils.c:370:3: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(tmpfilename,"%s_%s.%d.2", filter_temp, username,mypid);
data/filter-2.6.3+ds1/defs.h:227:15: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
extern char *getenv();
data/filter-2.6.3+ds1/filter.c:205:14: [3] (buffer) getopt:
Some older implementations do not protect against internal buffer overflows
(CWE-120, CWE-20). Check implementation on installation, or limit the size
of all string inputs.
while ((c = getopt(argc, argv, "chlm:no:qrSsvf:")) != EOF)
data/filter-2.6.3+ds1/filter.c:263:11: [3] (buffer) getenv:
Environment variables are untrustable input if they can be set by an
attacker. They can have any content and length, and the same variable can
be set more than once (CWE-807, CWE-20). Check environment variables
carefully before using them.
tmpstr=getenv("MAIL");
data/filter-2.6.3+ds1/actions.c:105: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[VERY_LONG_STRING];
data/filter-2.6.3+ds1/actions.c:214: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[VERY_LONG_STRING];
data/filter-2.6.3+ds1/actions.c:315:19: [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).
if ((mailunit = open(user_mailbox,
data/filter-2.6.3+ds1/actions.c:440: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[SLEN];
data/filter-2.6.3+ds1/actions.c:460:16: [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).
if ((fdunit = open(foldername,
data/filter-2.6.3+ds1/actions.c:509: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[SLEN];
data/filter-2.6.3+ds1/actions.c:573: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 mailbox[SLEN];
data/filter-2.6.3+ds1/actions.c:578:18: [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).
if ((mailunit = open(mailbox, O_APPEND | O_WRONLY | O_CREAT, 0600)) < 0) {
data/filter-2.6.3+ds1/actions.c:586:20: [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).
if ((mailunit = open(mailbox, O_APPEND | O_WRONLY | O_CREAT, 0600)) < 0) {
data/filter-2.6.3+ds1/audit.c:51: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.
static char date[NLEN];
data/filter-2.6.3+ds1/audit.c:69: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.
static char date[NLEN];
data/filter-2.6.3+ds1/buffer.c:24:1: [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 _vbuf[5*BUFSIZ]; /* space for file buffering */
data/filter-2.6.3+ds1/defs.h:194:14: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
extern void *memcpy(), *memset();
data/filter-2.6.3+ds1/defs.h:196:14: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
extern char *memcpy(), *memset();
data/filter-2.6.3+ds1/defs.h:202:9: [2] (buffer) bcopy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
#define bcopy(s1,s2,l) memcpy(s2,s1,l)
data/filter-2.6.3+ds1/defs.h:202:24: [2] (buffer) memcpy:
Does not check for buffer overflows when copying to destination (CWE-120).
Make sure destination can always hold the source data.
#define bcopy(s1,s2,l) memcpy(s2,s1,l)
data/filter-2.6.3+ds1/defs.h: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 from[STRING]; /** who sent the message? **/
data/filter-2.6.3+ds1/defs.h:335: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 to[STRING]; /** who it was sent to **/
data/filter-2.6.3+ds1/defs.h:336: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 messageid[STRING]; /** the Message-ID: value **/
data/filter-2.6.3+ds1/defs.h:337: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 time_zone[12]; /** incl. tz **/
data/filter-2.6.3+ds1/defs.h:339: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 time_menu[SHORT]; /** just the month..day for menu **/
data/filter-2.6.3+ds1/defs.h:341: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 subject[STRING]; /** The subject of the mail **/
data/filter-2.6.3+ds1/defs.h:342: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 mailx_status[WLEN];/** mailx status flags (RO...) **/
data/filter-2.6.3+ds1/defs.h:374: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 address[NLEN]; /* machine!user you get mail as */
data/filter-2.6.3+ds1/filter.c:164: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 action_argument[SLEN], /* action arg, per rule */
data/filter-2.6.3+ds1/filter.c:166: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 overridemailbox[MAX_LINE_LEN]; /* for -m option */
data/filter-2.6.3+ds1/filter.c:283: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 firstletter[2];
data/filter-2.6.3+ds1/filter.c:328: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).
if ((outfptr = fopen(outfname, "a")) == NULL) {
data/filter-2.6.3+ds1/filter.c: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 tmpsubj[LONG_STRING];
data/filter-2.6.3+ds1/filter.c:546: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 enc_bytes[2];
data/filter-2.6.3+ds1/filter.c:781: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[LONG_STRING];
data/filter-2.6.3+ds1/filter.h:228: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.
EXTERN char home[SLEN], /* the users home directory */
data/filter-2.6.3+ds1/filter.h:235: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.
EXTERN char rcpt_to[LONG_STRING],
data/filter-2.6.3+ds1/filter.h:242: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.
EXTERN char Efrom[LONG_STRING],
data/filter-2.6.3+ds1/filter.h:248: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.
EXTERN char outfname[SLEN]; /* logfile */
data/filter-2.6.3+ds1/filter.h:249: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.
EXTERN char filterfile[SLEN]; /* filter RULES file */
data/filter-2.6.3+ds1/filter.h:250: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.
EXTERN char filterlog[SLEN]; /* filter LOG file */
data/filter-2.6.3+ds1/filter.h:251: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.
EXTERN char filtersum[SLEN]; /* filter SUMMARY file */
data/filter-2.6.3+ds1/filter.h:252: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.
EXTERN char tmpfilename[SLEN]; /* dump mail to this file */
data/filter-2.6.3+ds1/filter.h:253: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.
EXTERN char user_mailbox[SLEN];
data/filter-2.6.3+ds1/filter.h:262: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 argument1[SLEN]; /* match against this */
data/filter-2.6.3+ds1/filter.h:271: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 argument2[SLEN]; /* argument for action */
data/filter-2.6.3+ds1/lock.c:97: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.
static char dotlock_name[SLEN];
data/filter-2.6.3+ds1/lock.c:204: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 pid_buffer[SHORT];
data/filter-2.6.3+ds1/lock.c:216:13: [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).
if((lockfd=open(lockfile,O_RDONLY)) == -1)
data/filter-2.6.3+ds1/lock.c:220:13: [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).
lockpid = atoi(pid_buffer);
data/filter-2.6.3+ds1/lock.c:265:13: [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).
flock_fd = open(fname, O_RDWR | O_CREAT, 0600);
data/filter-2.6.3+ds1/lock.c:356: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 maildir[SLEN];
data/filter-2.6.3+ds1/lock.c:380:18: [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).
while((lockfd = open(lockfile, O_WRONLY | O_CREAT | O_EXCL, 0444)) <0
data/filter-2.6.3+ds1/mk_lockname.c:27: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.
static char lock_name[SLEN];
data/filter-2.6.3+ds1/mk_lockname.c:46:9: [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(lock_name, "/tmp/%.10s.mlk", rindex(file_to_lock, '/')+1);
data/filter-2.6.3+ds1/parse.c:159: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
data/filter-2.6.3+ds1/parse.c:180: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).
if ((fd = fopen(filename,"r")) == NULL) {
data/filter-2.6.3+ds1/regexp.c:1153:9: [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 char buf[50];
data/filter-2.6.3+ds1/regexp.c:1197:3: [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(buf+strlen(buf), "OPEN%d", OP(op)-OPEN);
data/filter-2.6.3+ds1/regexp.c:1209:3: [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(buf+strlen(buf), "CLOSE%d", OP(op)-CLOSE);
data/filter-2.6.3+ds1/regexp.h:33: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 *startp[NSUBEXP];
data/filter-2.6.3+ds1/regexp.h:34: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 *endp[NSUBEXP];
data/filter-2.6.3+ds1/regexp.h:39: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 program[1]; /* Unwarranted chumminess with compiler. */
data/filter-2.6.3+ds1/rules.c:181:15: [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).
rule_lines = atoi(cond->argument1);
data/filter-2.6.3+ds1/rules.c:414:7: [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(&buffer[bufflen],"%2.2d",timerec->tm_mon+1);
data/filter-2.6.3+ds1/rules.c:581:9: [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 char buffer[10];
data/filter-2.6.3+ds1/rules.c:593:18: [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.
default : sprintf(buffer, "?%d?", n); return((char *)buffer);
data/filter-2.6.3+ds1/summarize.c: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[SLEN]; /* input buffer space */
data/filter-2.6.3+ds1/summarize.c:87: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).
if ((fd = fopen(filtersum, "r")) == NULL) {
data/filter-2.6.3+ds1/summarize.c:118:16: [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).
if ((rule = atoi(buffer)) > total_rules || rule < -1) {
data/filter-2.6.3+ds1/summarize.c:265:14: [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).
if ((fd = fopen(filterlog, "r")) == NULL) {
data/filter-2.6.3+ds1/utils.c:106:16: [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).
if ((fptr = fopen(filtersum, "a")) == NULL) {
data/filter-2.6.3+ds1/utils.c:120: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).
else if ((fptr = fopen(filterlog, "a")) == NULL) {
data/filter-2.6.3+ds1/utils.c:267:9: [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 char value[10];
data/filter-2.6.3+ds1/utils.c:270:4: [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(value, "%02d", i);
data/filter-2.6.3+ds1/utils.c:272:4: [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(value, "%d", i);
data/filter-2.6.3+ds1/utils.c:317: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 temp_filename[SLEN], *ptr;
data/filter-2.6.3+ds1/utils.c:368: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(tmpfilename, O_RDWR|O_CREAT|O_EXCL, 0600);
data/filter-2.6.3+ds1/utils.c:371:6: [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(tmpfilename, O_RDWR|O_CREAT|O_EXCL,0600);
data/filter-2.6.3+ds1/actions.c:174:17: [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).
in_header = (strlen(buffer) == 1? 0 : in_header);
data/filter-2.6.3+ds1/audit.c:60:26: [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).
if (!(stuff = malloc(strlen(username) + strlen(date) + 3)))
data/filter-2.6.3+ds1/audit.c:60:45: [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).
if (!(stuff = malloc(strlen(username) + strlen(date) + 3)))
data/filter-2.6.3+ds1/defs.h:172:9: [1] (buffer) equal:
Function does not check the second iterator for over-read conditions
(CWE-126). This function is often discouraged by most C++ coding standards
in favor of its safer alternatives provided since C++14. Consider using a
form of this function that checks the second iterator before potentially
overflowing it.
#define equal(s,w) (strcmp(s,w) == 0)
data/filter-2.6.3+ds1/defs.h:184:21: [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 lastch(s) s[strlen(s)-1]
data/filter-2.6.3+ds1/defs.h:253: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).
for (xyz=strlen(s)-1; xyz >= 0 && \
data/filter-2.6.3+ds1/defs.h:258:39: [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 first_word(s,w) (strncmp(s,w, strlen(w)) == 0)
data/filter-2.6.3+ds1/defs.h:259:43: [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 first_word_nc(s,w) (strincmp(s,w, strlen(w)) == 0)
data/filter-2.6.3+ds1/defs.h:426:40: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
char *strtok(), *strcpy(), *strcat(), *strncpy(); /* more in string.h in ANSI */
data/filter-2.6.3+ds1/defs.h:516:6: [1] (obsolete) ulimit:
This C routine is considered obsolete (as opposed to the shell command by
the same name, which is NOT obsolete) (CWE-676). Use getrlimit(2),
setrlimit(2), and sysconf(3) instead.
long ulimit();
data/filter-2.6.3+ds1/filter.c:145:29: [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).
register int skip = strlen(RCPT_TO_HDR);
data/filter-2.6.3+ds1/filter.c:291:35: [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).
stringcopy(user_mailbox,buffer,strlen(buffer)+1);
data/filter-2.6.3+ds1/filter.c:309:35: [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).
stringcopy(user_mailbox,buffer,strlen(buffer)+1);
data/filter-2.6.3+ds1/filter.c:407:15: [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).
else if (strlen(buffer) < 2)
data/filter-2.6.3+ds1/filter.c:636:24: [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).
stringcopy(dest, end, strlen(end)+1);
data/filter-2.6.3+ds1/filter.c:637:29: [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).
stringcopy(start, tmpsubj, strlen(tmpsubj)+1);
data/filter-2.6.3+ds1/filter.c:704: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).
to_len=strlen(strstart)+1;
data/filter-2.6.3+ds1/filter.c:745:12: [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).
field_len=strlen(strstart)+1;
data/filter-2.6.3+ds1/filter.c:787:13: [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).
if (buffer[strlen(buffer)-1] == '>') { /* case #1 */
data/filter-2.6.3+ds1/filter.c:788:11: [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).
for (i=strlen(buffer)-1; buffer[i] != '<' && i > 0; i--)
data/filter-2.6.3+ds1/filter.c:797:11: [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).
for (i=strlen(fieldname); whitespace(buffer[i]); i++)
data/filter-2.6.3+ds1/filter.h:98:37: [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 THE_SAME(a,b) (strncmp(a,b,strlen(b)) == 0)
data/filter-2.6.3+ds1/filter.h:104:44: [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 THE_SAMEHDR(a,b) (strncasecmp(a,b,strlen(b)) == 0)
data/filter-2.6.3+ds1/filter.h:111:34: [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 remove_return(s) { if (s[strlen(s)-1] == '\n') \
data/filter-2.6.3+ds1/filter.h:112:11: [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[strlen(s)-1] = '\0'; \
data/filter-2.6.3+ds1/lock.c:219:6: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
if (read(lockfd, pid_buffer, SHORT) > 0) {
data/filter-2.6.3+ds1/lock.c:303:10: [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 len=strlen(foldername);
data/filter-2.6.3+ds1/lock.c:335:10: [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 len=strlen(foldername);
data/filter-2.6.3+ds1/parse.c:209:13: [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).
buflen = strlen(buffer);
data/filter-2.6.3+ds1/parse.c:396: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).
if (word[strlen(word)-1] == '\\') /* If / was escaped ... */
data/filter-2.6.3+ds1/regexp.c:308:32: [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).
if (OP(scan) == EXACTLY && strlen(OPERAND(scan)) >= len) {
data/filter-2.6.3+ds1/regexp.c:310:12: [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).
len = strlen(OPERAND(scan));
data/filter-2.6.3+ds1/regexp.c:890:11: [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).
len = strlen(opnd);
data/filter-2.6.3+ds1/regexp.c:1045:11: [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).
count = strlen(scan);
data/filter-2.6.3+ds1/regexp.c:1197:15: [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).
sprintf(buf+strlen(buf), "OPEN%d", OP(op)-OPEN);
data/filter-2.6.3+ds1/regexp.c:1209:15: [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).
sprintf(buf+strlen(buf), "CLOSE%d", OP(op)-CLOSE);
data/filter-2.6.3+ds1/regexp.c:1223:10: [1] (buffer) strncat:
Easily used incorrectly (e.g., incorrectly computing the correct maximum
size to add) [MS-banned] (CWE-120). Consider strcat_s, strlcat, snprintf,
or automatically resizing strings.
(void) strncat(buf, p, 50);
data/filter-2.6.3+ds1/rules.c:327:20: [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).
for (i = 0, len = strlen(word); i < len; i++) {
data/filter-2.6.3+ds1/rules.c:345:15: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:356:29: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:369:29: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:385:29: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:395:29: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:405:29: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:415:29: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:425:29: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:437:29: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:447:29: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:460:29: [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).
bufflen = strlen(buffer);
data/filter-2.6.3+ds1/rules.c:478:17: [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).
bufflen = strlen(buffer);/* this is probably not used*/
data/filter-2.6.3+ds1/utils.c:133:13: [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).
subj_len = strlen(subject);
data/filter-2.6.3+ds1/utils.c:137:6: [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).
if (strlen(Hfrom) + subj_len > 60)
data/filter-2.6.3+ds1/utils.c:284:10: [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).
for (i= strlen(string); --i >= 0; )
data/filter-2.6.3+ds1/utils.c:298:2: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(dest, src, len);
data/filter-2.6.3+ds1/utils.c:324:24: [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).
ptr = temp_filename + strlen(temp_filename) - 1;
ANALYSIS SUMMARY:
Hits = 297
Lines analyzed = 6644 in approximately 0.23 seconds (29277 lines/second)
Physical Source Lines of Code (SLOC) = 4023
Hits@level = [0] 45 [1] 55 [2] 75 [3] 3 [4] 130 [5] 34
Hits@level+ = [0+] 342 [1+] 297 [2+] 242 [3+] 167 [4+] 164 [5+] 34
Hits/KSLOC@level+ = [0+] 85.0112 [1+] 73.8255 [2+] 60.1541 [3+] 41.5113 [4+] 40.7656 [5+] 8.4514
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.