You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Inconsistent direction of for loop (`cpp/inconsistent-loop-direction`) | Fewer false positive results | The query now accounts for intentional wrapping of an unsigned loop counter. |
17
+
| Overflow in uncontrolled allocation size (`cpp/uncontrolled-allocation-size`) || The precision of this query has been decreased from "high" to "medium". As a result, the query is still run but results are no longer displayed on LGTM by default. |
18
+
| Comparison result is always the same (`cpp/constant-comparison`) | More correct results | Bounds on expressions involving multiplication can now be determined in more cases. |
19
+
20
+
## Changes to libraries
21
+
22
+
* The models library now models more taint flows through `std::string`.
23
+
* The `SimpleRangeAnalysis` library now supports multiplications of the form
| Incomplete URL substring sanitization (`js/incomplete-url-substring-sanitization`) | More results | This query now recognizes additional URLs when the substring check is an inclusion check. |
<p>It is bad practice to use any of the <code>scanf</code> functions without including a specified length within the format parameter, as it will be vulnerable to buffer overflows.</p>
7
+
8
+
</overview>
9
+
10
+
<recommendation>
11
+
12
+
<p>Specify a length within the format string parameter, and make this length one less than the size of the buffer, since the last character should be reserved for the NULL terminator.</p>
13
+
14
+
</recommendation>
15
+
16
+
<example>
17
+
<p>The following example demonstrates safe and unsafe uses of <code>scanf</code> type functions.</p>
0 commit comments