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/xcal-4.1/patchlevel.h
Examining data/xcal-4.1/strfdate.c
Examining data/xcal-4.1/strftime/ptime.c
Examining data/xcal-4.1/strftime/strftime.c
Examining data/xcal-4.1/strftime/tzfile.h
Examining data/xcal-4.1/version.c
Examining data/xcal-4.1/xcal_buts.c
Examining data/xcal-4.1/xcal_cal/xcal_cal.c
Examining data/xcal-4.1/xcal_mmap.h
Examining data/xcal-4.1/xcalev/version.h
Examining data/xcal-4.1/xcalev/xcalev.c
Examining data/xcal-4.1/xcalpr/version.h
Examining data/xcal-4.1/xcalpr/xcal_days.c
Examining data/xcal-4.1/xcalpr/xcalpr.c
Examining data/xcal-4.1/xcal.h
Examining data/xcal-4.1/xcal_days.c
Examining data/xcal-4.1/xcal_help.c
Examining data/xcal-4.1/xcal_popup.c
Examining data/xcal-4.1/xcal_memo.c
Examining data/xcal-4.1/xcal_strip.c
Examining data/xcal-4.1/xcal.c
Examining data/xcal-4.1/xcal_alarm.c
Examining data/xcal-4.1/xcal_edit.c

FINAL RESULTS:

data/xcal-4.1/xcal.c:580:9:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
	(void) sprintf(us, " (%s)", appResources.otheruser);
data/xcal-4.1/xcal.c:583:19:  [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).
#define cstr(v) { strcpy(fmt, v); strcat(fmt, us); v = XtNewString(fmt); }
data/xcal-4.1/xcal.c:583:35:  [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).
#define cstr(v) { strcpy(fmt, v); strcat(fmt, us); v = XtNewString(fmt); }
data/xcal-4.1/xcal_alarm.c:61:45:  [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	dprintf	if (appResources.alarmScan) printf
data/xcal-4.1/xcal_alarm.c:197:11:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
			(void) sprintf(buf, "%s/xy%d/xc%d%s%d",
data/xcal-4.1/xcal_alarm.c:204:11:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
			(void) sprintf(buf, "%s/xc%d%s%d",
data/xcal-4.1/xcal_alarm.c:228:6:  [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(LocalMapStem, F_OK) == 0) {
data/xcal-4.1/xcal_alarm.c:236:6:  [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(TodayFile, F_OK) == 0) {
data/xcal-4.1/xcal_alarm.c:653:6:  [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.
					system(cmd);
data/xcal-4.1/xcal_alarm.c:661:6:  [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.
					system(cmd);
data/xcal-4.1/xcal_alarm.c:694:9:  [4] (format) sprintf:
  Potential format string problem (CWE-134). Make format string constant.
	(void) sprintf(buf, fmt, cmd);
data/xcal-4.1/xcal_alarm.c:847:10:  [4] (format) sprintf:
  Potential format string problem (CWE-134). Make format string constant.
		(void) sprintf(buf, fmt, tleft);
data/xcal-4.1/xcal_alarm.c:854:9:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
	(void) sprintf(buf, "%s\n%s\n", str1, str2);
data/xcal-4.1/xcal_cal/xcal_cal.c:127: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(usefile, file);
data/xcal-4.1/xcal_cal/xcal_cal.c:129:3:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		sprintf(usefile, "%s/%s", home, file);
data/xcal-4.1/xcal_cal/xcal_cal.c:163:3:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		sprintf(usedir, "%s/xy%4d", dir, year);
data/xcal-4.1/xcal_cal/xcal_cal.c:165:3:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		sprintf(usedir, "%s/%s/xy%4d", home, dir, year);
data/xcal-4.1/xcal_cal/xcal_cal.c:178:3:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		sprintf(usefile, "%s/%s", usedir, d->d_name);
data/xcal-4.1/xcal_edit.c:119:6:  [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(MapStem, F_OK) < 0)
data/xcal-4.1/xcal_edit.c:150:9:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
	(void) sprintf(buf, "%s/%s", pw->pw_dir, appResources.directory);
data/xcal-4.1/xcal_edit.c:198:9:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
	(void) sprintf(monthbuf, "%s", appResources.smon[mo]);
data/xcal-4.1/xcal_edit.c:476:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(fname, "%s/%s", dir, file);
data/xcal-4.1/xcal_edit.c:569: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(fname, F_OK) < 0) {
data/xcal-4.1/xcal_edit.c:583:9:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
	(void) sprintf(cname, "xc%d%s%d", day,
data/xcal-4.1/xcal_edit.c:587: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(fname, cname);
data/xcal-4.1/xcal_edit.c:631: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(fname, F_OK) < 0)
data/xcal-4.1/xcal_edit.c:635:9:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
	(void) sprintf(cname, "xc%d%s%d", day,
data/xcal-4.1/xcal_edit.c:639: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(fname, cname);
data/xcal-4.1/xcal_edit.c:705:9:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
	(void) sprintf(fname, "xw%s", appResources.sday[day]);
data/xcal-4.1/xcal_edit.c:723:6:  [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/xcal-4.1/xcal_edit.c:765: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(ed->ed_data, mw->mw_have[da->day]);
data/xcal-4.1/xcal_edit.c:912:10:  [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).
		(void) strcpy(buf, appResources.day[da->day]);
data/xcal-4.1/xcal_edit.c:993:2:  [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(mw->mw_have[day], ed->ed_data);
data/xcal-4.1/xcal_edit.c:1170:9:  [4] (format) sprintf:
  Potential format string problem (CWE-134). Make format string constant.
	(void) sprintf(buf, fmt, a, b);
data/xcal-4.1/xcal_edit.c:1212: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(newstr, mw->mw_have[da->day]);
data/xcal-4.1/xcal_edit.c:1217: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(newstr, txt);
data/xcal-4.1/xcal_memo.c:135:26:  [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 (FoundCalendarDir && access(appResources.memoFile, F_OK) == 0)
data/xcal-4.1/xcal_memo.c:165: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(memo.m_data, memoContents);
data/xcal-4.1/xcal_memo.c:504: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(memo.m_data, memoContents);
data/xcal-4.1/xcal_strip.c:207:10:  [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).
		(void) strcpy(iconName, appResources.weekly);
data/xcal-4.1/xcal_strip.c:225: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(titlestr, iconName);
data/xcal-4.1/xcal_strip.c:294:11:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
			(void) sprintf(titlestr, "%2d %s", i, dayStr);
data/xcal-4.1/xcal_strip.c:297:11:  [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).
			(void) strcpy(titlestr, dayStr);
data/xcal-4.1/xcalev/xcalev.c:180:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(buf, "%s/%s", pw->pw_dir, calendar);
data/xcal-4.1/xcalev/xcalev.c:187:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(buf, "%s/%s", calendar, regular);
data/xcal-4.1/xcalev/xcalev.c:217:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(buf, "%s/xc%%d%%s%d", calendar, year);
data/xcal-4.1/xcalev/xcalev.c:218:14:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
	else	(void) sprintf(buf, "%s/xy%d/xc%%d%%s%d", calendar, year, year);
data/xcal-4.1/xcalev/xcalev.c:223:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(buf, "%s/xy%d", calendar, year);
data/xcal-4.1/xcalev/xcalev.c:230:6:  [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(calendar, F_OK) < 0) {
data/xcal-4.1/xcalev/xcalev.c:240:6:  [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(caldir, F_OK) < 0) {
data/xcal-4.1/xcalev/xcalev.c:379:9:  [4] (format) sprintf:
  Potential format string problem (CWE-134). Make format string constant.
	(void) sprintf(filename, calfmt, day, months[mon]);
data/xcal-4.1/xcalev/xcalev.c:381:6:  [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(filename, F_OK) == 0) {
data/xcal-4.1/xcalev/xcalev.c:560: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, fmt, a, b, c);
data/xcal-4.1/xcalev/xcalev.c:572: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, fmt, a, b, c, d);
data/xcal-4.1/xcalpr/xcalpr.c:325:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(buf, "%s/%s", pw->pw_dir, calendar);
data/xcal-4.1/xcalpr/xcalpr.c:332:6:  [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(calendar, F_OK) < 0)
data/xcal-4.1/xcalpr/xcalpr.c:348:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(filename, "%s/xw%s", calendar, daynames[i]);
data/xcal-4.1/xcalpr/xcalpr.c:381:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(buf, "%s/xc%%d%%s%d", calendar, year);
data/xcal-4.1/xcalpr/xcalpr.c:382:14:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
	else	(void) sprintf(buf, "%s/xy%d/xc%%d%%s%d", calendar, year, year);
data/xcal-4.1/xcalpr/xcalpr.c:389:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(buf, "%s/xy%d", calendar, year);
data/xcal-4.1/xcalpr/xcalpr.c:411:9:  [4] (format) sprintf:
  Potential format string problem (CWE-134). Make format string constant.
	(void) sprintf(filename, calfmt, day, months[mn]);
data/xcal-4.1/xcalpr/xcalpr.c:453:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(prefix, "%s %02d\t", months[mn], day);
data/xcal-4.1/xcalpr/xcalpr.c:455:10:  [4] (buffer) sprintf:
  Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
  vsnprintf.
		(void) sprintf(prefix, "%s %02d %s %4d\t", daynames[wday],
data/xcal-4.1/xcalpr/xcalpr.c:558: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, fmt, a, b, c);
data/xcal-4.1/xcalpr/xcalpr.c:570: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, fmt, a, b, c, d);
data/xcal-4.1/xcal_cal/xcal_cal.c:86:8:  [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.
	char *getenv();
data/xcal-4.1/xcal_cal/xcal_cal.c:88:13:  [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, "d:f:m#")) != EOF) {
data/xcal-4.1/xcal_cal/xcal_cal.c:116:9:  [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.
	home = getenv("HOME");
data/xcal-4.1/xcalev/xcalev.c:117: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, "d:f:crv")) != EOF) {
data/xcal-4.1/xcalpr/xcalpr.c:134: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, "d:u:f:cxv")) != EOF) {
data/xcal-4.1/strfdate.c:181: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[10];
data/xcal-4.1/strftime/ptime.c:29: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	buf[512];
data/xcal-4.1/strftime/strftime.c:253: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[15];
data/xcal-4.1/strftime/strftime.c:271: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[10];
data/xcal-4.1/strftime/tzfile.h:55: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	tzh_reserved[24];	/* reserved for future use */
data/xcal-4.1/strftime/tzfile.h: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	tzh_ttisstdcnt[4];	/* coded number of trans. time flags */
data/xcal-4.1/strftime/tzfile.h:57: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	tzh_leapcnt[4];		/* coded number of leap seconds */
data/xcal-4.1/strftime/tzfile.h:58: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	tzh_timecnt[4];		/* coded number of transition times */
data/xcal-4.1/strftime/tzfile.h:59: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	tzh_typecnt[4];		/* coded number of local time types */
data/xcal-4.1/strftime/tzfile.h:60: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	tzh_charcnt[4];		/* coded number of abbr. chars */
data/xcal-4.1/xcal.c:66: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            date_area[BUFSIZ];
data/xcal-4.1/xcal.c:577: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	us[16];
data/xcal-4.1/xcal.c:578: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	fmt[256];
data/xcal-4.1/xcal.c:804: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[BUFSIZ];
data/xcal-4.1/xcal.c:827: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[BUFSIZ];
data/xcal-4.1/xcal_alarm.c:181: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/xcal-4.1/xcal_alarm.c:324: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            hrstr[16];
data/xcal-4.1/xcal_alarm.c:325: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            remline[256];
data/xcal-4.1/xcal_alarm.c:333: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 ((fp = fopen(file, "r")) == NULL) {
data/xcal-4.1/xcal_alarm.c:766: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[255];
data/xcal-4.1/xcal_cal/xcal_cal.c:67: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	usedir[MAXPATHLEN];
data/xcal-4.1/xcal_cal/xcal_cal.c:68: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	usefile[MAXPATHLEN];
data/xcal-4.1/xcal_cal/xcal_cal.c:69: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	line[BUFSIZ];
data/xcal-4.1/xcal_cal/xcal_cal.c:132: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((out = fopen(usefile, "w")) == NULL) {
data/xcal-4.1/xcal_cal/xcal_cal.c:158: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 day[3];
data/xcal-4.1/xcal_cal/xcal_cal.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 month[4];
data/xcal-4.1/xcal_cal/xcal_cal.c:181: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((in = fopen(usefile, "r")) == NULL) {
data/xcal-4.1/xcal_cal/xcal_cal.c:199:6:  [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).
		   atoi(day) < today) {
data/xcal-4.1/xcal_edit.c:137: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[BUFSIZ];
data/xcal-4.1/xcal_edit.c:185: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            yearbuf[5];
data/xcal-4.1/xcal_edit.c:186: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            monthbuf[4];
data/xcal-4.1/xcal_edit.c:197: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.
	(void) sprintf(yearbuf, "%d", yr);
data/xcal-4.1/xcal_edit.c:470: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            fname[256];
data/xcal-4.1/xcal_edit.c:479:12:  [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 ((fd = open(file, 0)) < 0) {
data/xcal-4.1/xcal_edit.c:544: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            fname[256];
data/xcal-4.1/xcal_edit.c:545: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            cname[16];
data/xcal-4.1/xcal_edit.c:567:10:  [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.
		(void) sprintf(fname, "xy%d", mw->mw_year);
data/xcal-4.1/xcal_edit.c:589:12:  [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 ((fd = open(fname, O_WRONLY | O_TRUNC | O_CREAT, 0666)) < 0) {
data/xcal-4.1/xcal_edit.c:619: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            fname[256];
data/xcal-4.1/xcal_edit.c:620: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            cname[16];
data/xcal-4.1/xcal_edit.c:629:10:  [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.
		(void) sprintf(fname, "xy%d", mw->mw_year);
data/xcal-4.1/xcal_edit.c:670: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 ((fd = open(fname, O_WRONLY | O_TRUNC | O_CREAT, 0666)) < 0) {
data/xcal-4.1/xcal_edit.c:703: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     fname[16];
data/xcal-4.1/xcal_edit.c:848: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[BUFSIZ];
data/xcal-4.1/xcal_edit.c:1168: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[BUFSIZ];
data/xcal-4.1/xcal_help.c:169: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(vers, version, vlen);
data/xcal-4.1/xcal_help.c:194: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 ((fd = open(appResources.helpfile, 0)) < 0)
data/xcal-4.1/xcal_memo.c:578:12:  [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 ((fd = open(fname, O_WRONLY | O_TRUNC | O_CREAT, 0666)) < 0) {
data/xcal-4.1/xcal_popup.c:284:8:  [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).
		mo = atoi(wk);
data/xcal-4.1/xcal_popup.c:309: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).
			da->year = atoi(wk);
data/xcal-4.1/xcal_popup.c:413: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     errmsg[256];
data/xcal-4.1/xcal_popup.c:426: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     errmsg[256];
data/xcal-4.1/xcal_strip.c:154: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            titlestr[256];
data/xcal-4.1/xcal_strip.c:155: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/xcal-4.1/xcal_strip.c:156: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            iconName[256];
data/xcal-4.1/xcal_strip.c:658: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(s, (char *)val, n);
data/xcal-4.1/xcalev/xcalev.c:115: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		line[BUFSIZ];
data/xcal-4.1/xcalev/xcalev.c:140: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).
		year = atoi(argv[optind]);
data/xcal-4.1/xcalev/xcalev.c:150:13:  [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 ((fin = fopen(regular, "r")) == NULL) {
data/xcal-4.1/xcalev/xcalev.c:168: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/xcal-4.1/xcalev/xcalev.c:306:9:  [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).
		day = atoi(ds);
data/xcal-4.1/xcalev/xcalev.c:307:12:  [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).
		dayend = atoi(p1);
data/xcal-4.1/xcalev/xcalev.c:313: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).
		day = dayend = atoi(ds);
data/xcal-4.1/xcalev/xcalev.c:372: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[256];
data/xcal-4.1/xcalev/xcalev.c:412:9:  [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).
	newf = fopen(filename, "a");
data/xcal-4.1/xcalev/xcalev.c:432: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 ((fd = open(filename, 0)) < 0) {
data/xcal-4.1/xcalev/xcalev.c:546:9:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	(void) memcpy(ret, str, len);
data/xcal-4.1/xcalpr/xcalpr.c:87: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	*dayfiles[7];		/* connected contents of any dayfiles */
data/xcal-4.1/xcalpr/xcalpr.c:144:11:  [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).
			fout = fopen(optarg, "w");
data/xcal-4.1/xcalpr/xcalpr.c:185: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).
				yr = atoi(argv[optind]);
data/xcal-4.1/xcalpr/xcalpr.c:307: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/xcal-4.1/xcalpr/xcalpr.c: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	filename[256];
data/xcal-4.1/xcalpr/xcalpr.c:378: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/xcal-4.1/xcalpr/xcalpr.c:406: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[256];
data/xcal-4.1/xcalpr/xcalpr.c:407: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	line[BUFSIZ];
data/xcal-4.1/xcalpr/xcalpr.c:412: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 (fin = fopen(filename, "r")) {
data/xcal-4.1/xcalpr/xcalpr.c:448: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	prefix[256];
data/xcal-4.1/xcalpr/xcalpr.c:487: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 ((fd = open(filename, 0)) < 0) {
data/xcal-4.1/xcalpr/xcalpr.c:544:9:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
	(void) memcpy(ret, str, len);
data/xcal-4.1/xcal_alarm.c:462:12:  [1] (buffer) getc:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
		if ((c = getc(fin)) == EOF) {
data/xcal-4.1/xcal_alarm.c:687: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).
	cmdlen = strlen(cmd);
data/xcal-4.1/xcal_alarm.c:688: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).
	arglen = arg ? strlen(arg) : 0;
data/xcal-4.1/xcal_alarm.c:701: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).
		d = buf + strlen(buf);
data/xcal-4.1/xcal_edit.c:219: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).
		switch (strlen(dp->d_name)) {
data/xcal-4.1/xcal_edit.c:496:6:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	if (read(fd, (String) destb, fsb.st_size) != fsb.st_size)
data/xcal-4.1/xcal_edit.c:547: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).
	len = strlen(contents);
data/xcal-4.1/xcal_edit.c:578:3:  [1] (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 character.
		strcat(fname, "/");
data/xcal-4.1/xcal_edit.c:633:3:  [1] (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 character.
		strcat(fname, "/");
data/xcal-4.1/xcal_edit.c:666: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).
	len = strlen(contents);
data/xcal-4.1/xcal_edit.c:763:42:  [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).
		ed->ed_size = appResources.textbufsz + strlen(mw->mw_have[da->day]) + 1;
data/xcal-4.1/xcal_edit.c:992:30:  [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).
	mw->mw_have[day] = XtMalloc(strlen(ed->ed_data) + 1);
data/xcal-4.1/xcal_edit.c:1208: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).
		srclen = strlen(mw->mw_have[da->day]);
data/xcal-4.1/xcal_edit.c:1210:19:  [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 = srclen + strlen(txt) +3;
data/xcal-4.1/xcal_help.c:136: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).
	vlen = strlen(version);
data/xcal-4.1/xcal_help.c:367:6:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	if (read(fd, base, len) != len)
data/xcal-4.1/xcal_memo.c:159:42:  [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).
		memo.m_size = appResources.textbufsz + strlen(memoContents) + 1;
data/xcal-4.1/xcal_memo.c:498: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).
		size = strlen(memoContents) + 1;
data/xcal-4.1/xcal_memo.c:562: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).
	Cardinal        len = strlen(memo->m_data);
data/xcal-4.1/xcalev/xcalev.c:478: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).
	len_of_txt = strlen(txt);
data/xcal-4.1/xcalev/xcalev.c:481:16:  [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_to_move = strlen(posn) - len_of_txt;
data/xcal-4.1/xcalev/xcalev.c:521: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).
	len = strlen(new);
data/xcal-4.1/xcalev/xcalev.c:542: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).
	len = strlen(str) + 1;
data/xcal-4.1/xcalev/xcalev.c:589:6:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	if (read(fd, base, len) != len)
data/xcal-4.1/xcalpr/xcalpr.c:540: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).
	len = strlen(str) + 1;
data/xcal-4.1/xcalpr/xcalpr.c:585:6:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
	if (read(fd, base, len) != len)

ANALYSIS SUMMARY:

Hits = 175
Lines analyzed = 8272 in approximately 0.22 seconds (37170 lines/second)
Physical Source Lines of Code (SLOC) = 5648
Hits@level = [0]  34 [1]  26 [2]  79 [3]   5 [4]  65 [5]   0
Hits@level+ = [0+] 209 [1+] 175 [2+] 149 [3+]  70 [4+]  65 [5+]   0
Hits/KSLOC@level+ = [0+] 37.0042 [1+] 30.9844 [2+] 26.381 [3+] 12.3938 [4+] 11.5085 [5+]   0
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.