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/r-bioc-rhdf5-2.34.0+dfsg/src/H5.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5A.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5A.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5D.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5D.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5F.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5F.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5G.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5G.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5I.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5I.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5L.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5L.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5O.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5O.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5P.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5P.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5S.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5S.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5T.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5T.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5Z.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5Z.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5constants.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/H5constants.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/HandleList.cpp
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/HandleList.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/HandleList2.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/HandleListWrap.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/HandleListcpp.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/external_filters.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/h5testLock.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/h5writeDataFrame.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/h5writeDataFrame.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/printdatatype.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/printdatatype.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/wrap.c
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/h5testLock.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/src/myhdf5.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5TSprivate.h
Examining data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h
FINAL RESULTS:
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:694:29: [5] (race) chmod:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchmod( ) instead.
#define HDchmod(S,M) chmod(S,M)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:697:31: [5] (race) chown:
This accepts filename arguments; if an attacker can move those files, a
race condition results. (CWE-362). Use fchown( ) instead.
#define HDchown(S,O,G) chown(S,O,G)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:980:26: [5] (buffer) gets:
Does not check for buffer overflows (CWE-120, CWE-20). Use fgets() instead.
#define HDgets(S) gets(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:246:9: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(p_event_start, "start %s", FUNC); \
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:624:30: [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.
#define HDaccess(F,M) access(F, M)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:727:29: [4] (misc) cuserid:
Exactly what cuserid() does is poorly defined (e.g., some systems use the
effective uid, like Linux, while others like System V use the real uid).
Thus, you can't trust what it does. It's certainly not portable (The
cuserid function was included in the 1988 version of POSIX, but removed
from the 1990 version). Also, if passed a non-null parameter, there's a
risk of a buffer overflow if the passed-in buffer is not at least L_cuserid
characters long (CWE-120). Use getpwuid(geteuid()) and extract the desired
information instead.
#define HDcuserid(S) cuserid(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:749:30: [4] (shell) execv:
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.
#define HDexecv(S,AV) execv(S,AV)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:755:31: [4] (shell) execvp:
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.
#define HDexecvp(S,AV) execvp(S,AV)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:959:29: [4] (misc) getlogin:
It's often easy to fool getlogin. Sometimes it does not work at all,
because some program messed up the utmp file. Often, it gives only the
first 8 characters of the login name. The user currently logged in on the
controlling tty of our program need not be the user who started it. Avoid
getlogin() for security-related purposes (CWE-807). Use getpwuid(geteuid())
and extract the desired information instead.
#define HDgetlogin() getlogin()
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1301:27: [4] (format) snprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define HDsnprintf snprintf /*varargs*/
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1304:26: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
#define HDsprintf sprintf /*varargs*/
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1332:30: [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 HDstrcat(X,Y) strcat(X,Y)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1347:30: [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 HDstrcpy(X,Y) strcpy(X,Y)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1416:28: [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.
#define HDsystem(S) system(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1500:34: [4] (format) vfprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
#define HDvfprintf(F,FMT,A) vfprintf(F,FMT,A)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1503:31: [4] (format) vprintf:
If format strings can be influenced by an attacker, they can be exploited
(CWE-134). Use a constant for the format specification.
#define HDvprintf(FMT,A) vprintf(FMT,A)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1506:34: [4] (format) vsprintf:
Potential format string problem (CWE-134). Make format string constant.
#define HDvsprintf(S,FMT,A) vsprintf(S,FMT,A)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1509:36: [4] (format) vsnprintf:
If format strings can be influenced by an attacker, they can be exploited,
and note that sprintf variations do not always \0-terminate (CWE-134). Use
a constant for the format specification.
#define HDvsnprintf(S,N,FMT,A) vsnprintf(S,N,FMT,A)
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5A.c:325:5: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(str, "Reading attribute data of type '%s' not yet implemented. Values replaced by NA's.", getDatatypeClass(dtype_id));
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5D.c:570:9: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(str, "h5read for type ENUM [%s] not yet implemented. Values replaced by NA's.", getDatatypeClass(H5Tget_super( dtype_id )));
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5D.c:700:13: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(str, "h5read for type ARRAY [%s] not yet implemented. Values replaced by NA's.", getDatatypeClass(H5Tget_super( dtype_id )));
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5D.c:829:9: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf(str, "h5read for type '%s' not yet implemented. Values replaced by NA's.", getDatatypeClass(dtype_id));
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:55:9: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf (cd->txt[cd->n],"%*serror #%03d: %s in %s(): line %u",
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:58:9: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf (cd->txt[cd->n+1],"%*sclass: %s", indent*2, "", cls);
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:59:9: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf (cd->txt[cd->n+2],"%*smajor: %s", indent*2, "", maj);
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:60:9: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf (cd->txt[cd->n+3],"%*sminor: %s", indent*2, "", min);
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:92:9: [4] (buffer) sprintf:
Does not check for buffer overflows (CWE-120). Use sprintf_s, snprintf, or
vsnprintf.
sprintf (cd->txt[cd->n],"%s. %s. %s.", cls, maj, min);
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:121:17: [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(str, client_data.txt[i]);
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:152:17: [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(str, client_data.txt[i]);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:22:5: [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(newElement->name, name);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:24:5: [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(newElement->group, data->group);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:71:21: [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(data->group, group);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:75:21: [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(data->group, name);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:22:5: [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(newElement->name, name);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:24:5: [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(newElement->group, data->group);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:61:21: [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(data->group, group);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:65:21: [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(data->group, name);
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:51:9: [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(newElement->dim, tmp);
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:67:9: [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(newElement->maxdim, tmp);
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5TSprivate.h:61:32: [3] (misc) InitializeCriticalSection:
Exceptions can be thrown in low-memory situations. Use
InitializeCriticalSectionAndSpinCount instead.
#define H5TS_mutex_init(mutex) InitializeCriticalSection(mutex)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5TSprivate.h:62:39: [3] (misc) EnterCriticalSection:
On some versions of Windows, exceptions can be thrown in low-memory
situations. Use InitializeCriticalSectionAndSpinCount instead.
#define H5TS_mutex_lock_simple(mutex) EnterCriticalSection(mutex)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:938:28: [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.
#define HDgetenv(S) getenv(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1177:29: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
#define HDrand() random()
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1180:31: [3] (random) random:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
#define HDrandom() random()
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1201:34: [3] (buffer) realpath:
This function does not protect against buffer overflows, and some
implementations can overflow internally (CWE-120/CWE-785!). Ensure that the
destination buffer is at least of size MAXPATHLEN, andto protect against
implementation problems, the input argument should also be checked to
ensure it is no larger than MAXPATHLEN.
#define HDrealpath(F1,F2) realpath(F1,F2)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1316:31: [3] (random) srandom:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
#define HDsrand(S) srandom(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1319:33: [3] (random) srandom:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
#define HDsrandom(S) srandom(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1323:31: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
#define HDsrand(S) srand(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1326:33: [3] (random) srand:
This function is not sufficiently random for security-related functions
such as key and nonce creation (CWE-327). Use a more secure technique for
acquiring random values.
#define HDsrandom(S) srand(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1458:28: [3] (tmpfile) tmpnam:
Temporary file race condition (CWE-377).
#define HDtmpnam(S) tmpnam(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:235:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char p_event_start[128];
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:661:26: [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).
#define HDatoi(S) atoi(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:664:26: [2] (integer) atol:
Unless checked, the resulting number can exceed the expected range
(CWE-190). If source untrusted, check both minimum and maximum, even if the
input had no minus sign (large numbers can roll over into negative number;
consider saving to an unsigned value if that is intended).
#define HDatol(S) atol(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:840:29: [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).
#define HDfopen(S,M) fopen(S,M)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1104:32: [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 HDmemcpy(X,Y,Z) memcpy((char*)(X),(const char*)(Y),Z)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1128:30: [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).
#define HDopen(F,...) open(F,__VA_ARGS__)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1455:28: [2] (tmpfile) tmpfile:
Function tmpfile() has a security flaw on some systems (e.g., older System
V systems) (CWE-377).
#define HDtmpfile() tmpfile()
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1855:18: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
'_'!=((const char *)S)[2] /* underscore at position 2 */ \
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1856:21: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
&& '_'!=((const char *)S)[3] /* underscore at position 3 */ \
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1858:17: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
((const char *)S)[4] /* pos 4 exists */ \
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1860:25: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
&& '_'==((const char *)S)[4] /* pos 4 underscore */ \
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5A.c:201:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char *bufSTR[n];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5A.c:208:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char bufSTR[n][size];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5A.c:210:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char bufSTR2[n][size+1];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5A.c:324:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char str[256];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5A.c:442:3: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char buf[s+1];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5D.c:569: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.
char str[256];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5D.c:699:13: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char str[256];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5D.c:828: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.
char str[256];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:30: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 txt[401][1024];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:35:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char maj[MSG_SIZE];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:36:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char min[MSG_SIZE];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:37:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char cls[MSG_SIZE];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:52:9: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(cd->txt[cd->n]," ... [truncated]\n");
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:72:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char maj[MSG_SIZE];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:73:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char min[MSG_SIZE];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:74:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char cls[MSG_SIZE];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:89:9: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(cd->txt[cd->n]," ... [truncated]\n");
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:117:13: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char str[L];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:118:13: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(str, "libhdf5");
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:148:13: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char str[L];
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:149:13: [2] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant string.
strcpy(str, "libhdf5");
data/r-bioc-rhdf5-2.34.0+dfsg/src/HandleListWrap.c:34:17: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char n1[st];
data/r-bioc-rhdf5-2.34.0+dfsg/src/HandleListWrap.c:85:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char n1[st+1];
data/r-bioc-rhdf5-2.34.0+dfsg/src/HandleListWrap.c:137:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char name[1024];
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5testLock.h:10:30: [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).
#define HDopen(F,...) open(F,__VA_ARGS__)
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5writeDataFrame.c:125:30: [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 * strbuf = (char *)R_alloc(n,strsize[i]);
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:7:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tmp[1000];
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:20:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tmp[1000];
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:54:13: [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(tmp, "UNLIMITED");
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.h:15:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char spacetype[20];
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.h:17:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char dim[1000];
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.h:18:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char maxdim[1000];
data/r-bioc-rhdf5-2.34.0+dfsg/src/wrap.c:324:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tmp_string[21];
data/r-bioc-rhdf5-2.34.0+dfsg/src/wrap.c:325:5: [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(tmp_string, "%lld", (long long) hid);
data/r-bioc-rhdf5-2.34.0+dfsg/src/wrap.c:330:5: [2] (buffer) char:
Statically-sized arrays can be improperly restricted, leading to potential
overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
functions that limit length, or ensure that the size is larger than the
maximum possible length.
char tmp_string[21];
data/r-bioc-rhdf5-2.34.0+dfsg/src/wrap.c:331:5: [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(tmp_string, "%lld", (long long) hid);
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:800:27: [1] (buffer) fgetc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#define HDfgetc(F) fgetc(F)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:920:26: [1] (buffer) getc:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#define HDgetc(F) getc(F)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:923:28: [1] (buffer) getchar:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#define HDgetchar() getchar()
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1192:30: [1] (buffer) read:
Check buffer boundaries if used in a loop including recursive loops
(CWE-120, CWE-20).
#define HDread(F,M,Z) read(F,M,Z)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1359:28: [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 HDstrlen(S) strlen(S)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1362:31: [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.
#define HDstrncat(X,Y,Z) strncat(X,Y,Z)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1368:31: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
#define HDstrncpy(X,Y,Z) strncpy(X,Y,Z)
data/r-bioc-rhdf5-2.34.0+dfsg/debian/hdf5-private/H5private.h:1473:27: [1] (access) umask:
Ensure that umask is given most restrictive possible setting (e.g., 066 or
077) (CWE-732).
#define HDumask(N) umask(N)
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:114: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).
L = L + strlen(client_data.txt[i]) + 2;
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:120:17: [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(str, "\n");
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:145: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).
L = L + strlen(client_data.txt[i]) + 2;
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5E.c:151:17: [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(str, "\n");
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5P.c:724:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(fa.aws_region, the_region, H5FD_ROS3_MAX_REGION_LEN);
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5P.c:725:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(fa.secret_id, the_access_key_id, H5FD_ROS3_MAX_SECRET_ID_LEN);
data/r-bioc-rhdf5-2.34.0+dfsg/src/H5P.c:726:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(fa.secret_key, the_secret_access_key, H5FD_ROS3_MAX_SECRET_KEY_LEN);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:21: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).
newElement->name = (char *) R_alloc((strlen(name)+1), sizeof(char));
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:23: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).
newElement->group = (char *) R_alloc((strlen(data->group)+1), sizeof(char));
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:42:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(newElement->datatype, "", 1);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:44:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(newElement->dataclass, "", 1);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:46:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(newElement->spacetype, "\0", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:47:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(newElement->dim, "", 100);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:48:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(newElement->maxdim, "", 100);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:70:53: [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).
data->group = (char *) R_alloc((strlen(name)+strlen(group)+2), sizeof(char));
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:70:66: [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).
data->group = (char *) R_alloc((strlen(name)+strlen(group)+2), sizeof(char));
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:73:25: [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(data->group, "/");
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:109:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->spacetype, "SCALAR", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:112:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->spacetype, "SIMPLE", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:115:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->spacetype, "NULL", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:118:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->spacetype, "NO_CLASS", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:121:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->spacetype, "unknown dataspace", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5dump.c:236:5: [1] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant character.
strcpy(data.group, "/");
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:21: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).
newElement->name = (char *) R_alloc(1, (strlen(name)+1) * sizeof(char));
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:23:46: [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).
newElement->group = (char *) R_alloc(1, (strlen(data->group)+1) * sizeof(char));
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:42:13: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(newElement->datatype, "", 1);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:44:13: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(newElement->dataclass, "", 1);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:46:13: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(newElement->spacetype, "\0", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:47:13: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(newElement->dim, "", 100);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:48:13: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant character.
strncpy(newElement->maxdim, "", 100);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:60:52: [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).
data->group = (char *)R_alloc((strlen(name)+strlen(group)+2), sizeof(char));
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:60:65: [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).
data->group = (char *)R_alloc((strlen(name)+strlen(group)+2), sizeof(char));
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:63:25: [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(data->group, "/");
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:96:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->spacetype, "SCALAR", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:99:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->spacetype, "SIMPLE", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:102:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->spacetype, "NULL", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:105:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->spacetype, "NO_CLASS", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:108:17: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->spacetype, "unknown dataspace", 20);
data/r-bioc-rhdf5-2.34.0+dfsg/src/h5ls.c:144:9: [1] (buffer) strcpy:
Does not check for buffer overflows when copying to destination [MS-banned]
(CWE-120). Consider using snprintf, strcpy_s, or strlcpy (warning: strncpy
easily misused). Risk is low because the source is a constant character.
strcpy(data.group, "/");
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:9:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(tmp, s1, 999);
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:22:5: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120).
strncpy(tmp, s1, 999);
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:36:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->dim, "( 0 )", 1000);
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:37:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->maxdim, "( 0 )", 1000);
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:75:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->dim, "unknown dataspace", 1000);
data/r-bioc-rhdf5-2.34.0+dfsg/src/utils.c:76:9: [1] (buffer) strncpy:
Easily used incorrectly; doesn't always \0-terminate or check for invalid
pointers [MS-banned] (CWE-120). Risk is low because the source is a
constant string.
strncpy(newElement->maxdim, "unknown dataspace", 1000);
ANALYSIS SUMMARY:
Hits = 150
Lines analyzed = 10688 in approximately 0.36 seconds (29736 lines/second)
Physical Source Lines of Code (SLOC) = 6371
Hits@level = [0] 5 [1] 53 [2] 47 [3] 11 [4] 36 [5] 3
Hits@level+ = [0+] 155 [1+] 150 [2+] 97 [3+] 50 [4+] 39 [5+] 3
Hits/KSLOC@level+ = [0+] 24.329 [1+] 23.5442 [2+] 15.2252 [3+] 7.84806 [4+] 6.12149 [5+] 0.470884
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.