Skip to content

Commit 64fed4c

Browse files
authored
Merge pull request #5677 from MathiasVP/fix-duplicate-ids-in-experimental
C++: Fix duplicate names in experimental queries
2 parents b4f01c9 + 53a320a commit 64fed4c

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

cpp/ql/src/experimental/Security/CWE/CWE-788/AccessOfMemoryLocationAfterEndOfBufferUsingStrlen.ql

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
* @description The expression `buffer [strlen (buffer)] = 0` is potentially dangerous, if the variable `buffer` does not have a terminal zero, then access beyond the bounds of the allocated memory is possible, which will lead to undefined behavior.
44
* If terminal zero is present, then the specified expression is meaningless.
55
* @kind problem
6-
* @id cpp/access-memory-location-after-end-buffer
6+
* @id cpp/access-memory-location-after-end-buffer-strlen
77
* @problem.severity warning
88
* @precision medium
99
* @tags correctness

cpp/ql/src/experimental/Security/CWE/CWE-788/AccessOfMemoryLocationAfterEndOfBufferUsingStrncat.ql

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
* @name Access Of Memory Location After The End Of A Buffer Using Strncat
33
* @description Calls of the form `strncat(dest, source, sizeof (dest) - strlen (dest))` set the third argument to one more than possible. So when `dest` is full, the expression `sizeof(dest) - strlen (dest)` will be equal to one, and not zero as the programmer might think. Making a call of this type may result in a zero byte being written just outside the `dest` buffer.
44
* @kind problem
5-
* @id cpp/access-memory-location-after-end-buffer
5+
* @id cpp/access-memory-location-after-end-buffer-strncat
66
* @problem.severity warning
77
* @precision medium
88
* @tags correctness

0 commit comments

Comments
 (0)