-
Notifications
You must be signed in to change notification settings - Fork 67
Implement Memory3 and InvalidMemory2 packages #274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
5928bcc
Define InvalidMemory2 and Memory3 packages
1939ec2
InvalidMemory2: Implement ARR32-C query
11a6941
Memory3: Implement MEM35-C query
371c778
InvalidMemory2: Implement ARR37-C query
888b054
InvalidMemory2: Implement EXP35-C query
163e23f
Update DoNotModifyObjectsWithTemporaryLifetime.md
b42eeb2
Merge branch 'main' into Memory3
lcartey File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -242,6 +242,7 @@ | |
"Macros", | ||
"Memory1", | ||
"Memory2", | ||
"Memory3", | ||
"Misc", | ||
"MoveForward", | ||
"Naming", | ||
|
194 changes: 194 additions & 0 deletions
194
c/cert/src/rules/ARR32-C/VariableLengthArraySizeNotInValidRange.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,194 @@ | ||
# ARR32-C: Ensure size arguments for variable length arrays are in a valid range | ||
|
||
This query implements the CERT-C rule ARR32-C: | ||
|
||
> Ensure size arguments for variable length arrays are in a valid range | ||
|
||
|
||
## Description | ||
|
||
Variable length arrays (VLAs), a conditionally supported language feature, are essentially the same as traditional C arrays except that they are declared with a size that is not a constant integer expression and can be declared only at block scope or function prototype scope and no linkage. When supported, a variable length array can be declared | ||
|
||
```cpp | ||
{ /* Block scope */ | ||
char vla[size]; | ||
} | ||
|
||
``` | ||
where the integer expression `size` and the declaration of `vla` are both evaluated at runtime. If the size argument supplied to a variable length array is not a positive integer value, the behavior is undefined. (See [undefined behavior 75](https://wiki.sei.cmu.edu/confluence/display/c/CC.+Undefined+Behavior#CC.UndefinedBehavior-ub_75).) Additionally, if the magnitude of the argument is excessive, the program may behave in an unexpected way. An attacker may be able to leverage this behavior to overwrite critical program data \[[Griffiths 2006](https://wiki.sei.cmu.edu/confluence/display/c/AA.+Bibliography#AA.Bibliography-Griffiths06)\]. The programmer must ensure that size arguments to variable length arrays, especially those derived from untrusted data, are in a valid range. | ||
|
||
Because variable length arrays are a conditionally supported feature of C11, their use in portable code should be guarded by testing the value of the macro `__STDC_NO_VLA__`. Implementations that do not support variable length arrays indicate it by setting `__STDC_NO_VLA__` to the integer constant 1. | ||
|
||
## Noncompliant Code Example | ||
|
||
In this noncompliant code example, a variable length array of size `size` is declared. The `size` is declared as `size_t` in compliance with [INT01-C. Use rsize_t or size_t for all integer values representing the size of an object](https://wiki.sei.cmu.edu/confluence/display/c/INT01-C.+Use+rsize_t+or+size_t+for+all+integer+values+representing+the+size+of+an+object). | ||
|
||
```cpp | ||
#include <stddef.h> | ||
|
||
extern void do_work(int *array, size_t size); | ||
|
||
void func(size_t size) { | ||
int vla[size]; | ||
do_work(vla, size); | ||
} | ||
|
||
``` | ||
However, the value of `size` may be zero or excessive, potentially giving rise to a security [vulnerability](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-vulnerability). | ||
|
||
## Compliant Solution | ||
|
||
This compliant solution ensures the `size` argument used to allocate `vla` is in a valid range (between 1 and a programmer-defined maximum); otherwise, it uses an algorithm that relies on dynamic memory allocation. The solution also avoids unsigned integer wrapping that, given a sufficiently large value of `size`, would cause `malloc` to allocate insufficient storage for the array. | ||
|
||
```cpp | ||
#include <stdint.h> | ||
#include <stdlib.h> | ||
|
||
enum { MAX_ARRAY = 1024 }; | ||
extern void do_work(int *array, size_t size); | ||
|
||
void func(size_t size) { | ||
if (0 == size || SIZE_MAX / sizeof(int) < size) { | ||
/* Handle error */ | ||
return; | ||
} | ||
if (size < MAX_ARRAY) { | ||
int vla[size]; | ||
do_work(vla, size); | ||
} else { | ||
int *array = (int *)malloc(size * sizeof(int)); | ||
if (array == NULL) { | ||
/* Handle error */ | ||
} | ||
do_work(array, size); | ||
free(array); | ||
} | ||
} | ||
|
||
``` | ||
|
||
## Noncompliant Code Example (sizeof) | ||
|
||
The following noncompliant code example defines `A` to be a variable length array and then uses the `sizeof` operator to compute its size at runtime. When the function is called with an argument greater than `SIZE_MAX / (N1 * sizeof (int))`, the runtime `sizeof` expression may wrap around, yielding a result that is smaller than the mathematical product `N1 * n2 * sizeof (int)`. The call to `malloc()`, when successful, will then allocate storage for fewer than `n2` elements of the array, causing one or more of the final `memset()` calls in the `for` loop to write past the end of that storage. | ||
|
||
```cpp | ||
#include <stdlib.h> | ||
#include <string.h> | ||
|
||
enum { N1 = 4096 }; | ||
|
||
void *func(size_t n2) { | ||
typedef int A[n2][N1]; | ||
|
||
A *array = malloc(sizeof(A)); | ||
if (!array) { | ||
/* Handle error */ | ||
return NULL; | ||
} | ||
|
||
for (size_t i = 0; i != n2; ++i) { | ||
memset(array[i], 0, N1 * sizeof(int)); | ||
} | ||
|
||
return array; | ||
} | ||
|
||
``` | ||
Furthermore, this code also violates [ARR39-C. Do not add or subtract a scaled integer to a pointer](https://wiki.sei.cmu.edu/confluence/display/c/ARR39-C.+Do+not+add+or+subtract+a+scaled+integer+to+a+pointer), where `array` is a pointer to the two-dimensional array, where it should really be a pointer to the latter dimension instead. This means that the `memset() `call does out-of-bounds writes on all of its invocations except the first. | ||
|
||
## Compliant Solution (sizeof) | ||
|
||
This compliant solution prevents `sizeof` wrapping by detecting the condition before it occurs and avoiding the subsequent computation when the condition is detected. The code also uses an additional typedef to fix the type of `array` so that `memset()` never writes past the two-dimensional array. | ||
|
||
```cpp | ||
#include <stdint.h> | ||
#include <stdlib.h> | ||
#include <string.h> | ||
|
||
enum { N1 = 4096 }; | ||
|
||
void *func(size_t n2) { | ||
if (n2 > SIZE_MAX / (N1 * sizeof(int))) { | ||
/* Prevent sizeof wrapping */ | ||
return NULL; | ||
} | ||
|
||
typedef int A1[N1]; | ||
typedef A1 A[n2]; | ||
|
||
A1 *array = (A1*) malloc(sizeof(A)); | ||
|
||
if (!array) { | ||
/* Handle error */ | ||
return NULL; | ||
} | ||
|
||
for (size_t i = 0; i != n2; ++i) { | ||
memset(array[i], 0, N1 * sizeof(int)); | ||
} | ||
return array; | ||
} | ||
|
||
``` | ||
**Implementation Details** | ||
|
||
**Microsoft** | ||
|
||
Variable length arrays are not supported by Microsoft compilers. | ||
|
||
## Risk Assessment | ||
|
||
Failure to properly specify the size of a variable length array may allow arbitrary code execution or result in stack exhaustion. | ||
|
||
<table> <tbody> <tr> <th> Rule </th> <th> Severity </th> <th> Likelihood </th> <th> Remediation Cost </th> <th> Priority </th> <th> Level </th> </tr> <tr> <td> ARR32-C </td> <td> High </td> <td> Probable </td> <td> High </td> <td> <strong>P6</strong> </td> <td> <strong>L2</strong> </td> </tr> </tbody> </table> | ||
|
||
|
||
## Automated Detection | ||
|
||
<table> <tbody> <tr> <th> Tool </th> <th> Version </th> <th> Checker </th> <th> Description </th> </tr> <tr> <td> <a> CodeSonar </a> </td> <td> 7.2p0 </td> <td> <strong>ALLOC.SIZE.IOFLOWALLOC.SIZE.MULOFLOWMISC.MEM.SIZE.BAD</strong> </td> <td> Integer Overflow of Allocation Size Multiplication Overflow of Allocation Size Unreasonable Size Argument </td> </tr> <tr> <td> <a> Coverity </a> </td> <td> 2017.07 </td> <td> <strong>REVERSE_NEGATIVE</strong> </td> <td> Fully implemented </td> </tr> <tr> <td> <a> Helix QAC </a> </td> <td> 2022.4 </td> <td> <strong>C1051</strong> </td> <td> </td> </tr> <tr> <td> <a> Klocwork </a> </td> <td> 2022.4 </td> <td> <strong>MISRA.ARRAY.VAR_LENGTH.2012</strong> </td> <td> </td> </tr> <tr> <td> <a> LDRA tool suite </a> </td> <td> 9.7.1 </td> <td> <strong>621 S</strong> </td> <td> Enhanced enforcement </td> </tr> <tr> <td> <a> Parasoft C/C++test </a> </td> <td> 2022.2 </td> <td> <strong>CERT_C-ARR32-a</strong> </td> <td> Ensure the size of the variable length array is in valid range </td> </tr> <tr> <td> <a> PC-lint Plus </a> </td> <td> 1.4 </td> <td> <strong>9035</strong> </td> <td> Assistance provided </td> </tr> <tr> <td> <a> Polyspace Bug Finder </a> </td> <td> R2023a </td> <td> <a> CERT C: Rule ARR32-C </a> </td> <td> Checks for: Memory allocation with tainted sizeemory allocation with tainted size, tainted size of variable length arrayainted size of variable length array. Rule fully covered. </td> </tr> <tr> <td> <a> PRQA QA-C </a> </td> <td> 9.7 </td> <td> <strong>1051</strong> </td> <td> Partially implemented </td> </tr> <tr> <td> <a> Cppcheck </a> </td> <td> 1.66 </td> <td> <strong>negativeArraySize</strong> </td> <td> Context sensitive analysis Will warn only if given size is negative </td> </tr> <tr> <td> <a> TrustInSoft Analyzer </a> </td> <td> 1.38 </td> <td> <strong>alloca_bounds</strong> </td> <td> Exhaustively verified. </td> </tr> </tbody> </table> | ||
|
||
|
||
## Related Vulnerabilities | ||
|
||
Search for [vulnerabilities](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-vulnerability) resulting from the violation of this rule on the [CERT website](https://www.kb.cert.org/vulnotes/bymetric?searchview&query=FIELD+KEYWORDS+contains+ARR32-C). | ||
|
||
## Related Guidelines | ||
|
||
[Key here](https://wiki.sei.cmu.edu/confluence/display/c/How+this+Coding+Standard+is+Organized#HowthisCodingStandardisOrganized-RelatedGuidelines) (explains table format and definitions) | ||
|
||
<table> <tbody> <tr> <th> Taxonomy </th> <th> Taxonomy item </th> <th> Relationship </th> </tr> <tr> <td> <a> CERT C Secure Coding Standard </a> </td> <td> <a> INT01-C. Use rsize_t or size_t for all integer values representing the size of an object </a> </td> <td> Prior to 2018-01-12: CERT: Unspecified Relationship </td> </tr> <tr> <td> <a> ISO/IEC TR 24772:2013 </a> </td> <td> Unchecked Array Indexing \[XYZ\] </td> <td> Prior to 2018-01-12: CERT: Unspecified Relationship </td> </tr> <tr> <td> <a> ISO/IEC TS 17961:2013 </a> </td> <td> Tainted, potentially mutilated, or out-of-domain integer values are used in a restricted sink \[taintsink\] </td> <td> Prior to 2018-01-12: CERT: Unspecified Relationship </td> </tr> <tr> <td> <a> CWE 2.11 </a> </td> <td> <a> CWE-758 </a> </td> <td> 2017-06-29: CERT: Rule subset of CWE </td> </tr> </tbody> </table> | ||
|
||
|
||
## CERT-CWE Mapping Notes | ||
|
||
[Key here](https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87152408#HowthisCodingStandardisOrganized-CERT-CWEMappingNotes) for mapping notes | ||
|
||
**CWE-129 and ARR32-C** | ||
|
||
Intersection( CWE-188, EXP39-C) = Ø | ||
|
||
ARR32-C addresses specifying the size of a variable-length array (VLA). CWE-129 addresses invalid array indices, not array sizes. | ||
|
||
**CWE-758 and ARR32-C** | ||
|
||
Independent( INT34-C, INT36-C, MSC37-C, FLP32-C, EXP33-C, EXP30-C, ERR34-C, ARR32-C) | ||
|
||
CWE-758 = Union( ARR32-C, list) where list = | ||
|
||
* Undefined behavior that results from anything other than too large a VLA dimension. | ||
**CWE-119 and ARR32-C** | ||
* Intersection( CWE-119, ARR32-C) = Ø | ||
* ARR32-C is not about providing a valid buffer but reading/writing outside it. It is about providing an invalid buffer, or one that exhausts the stack. | ||
|
||
## Bibliography | ||
|
||
<table> <tbody> <tr> <td> \[ <a> Griffiths 2006 </a> \] </td> </tr> </tbody> </table> | ||
|
||
|
||
## Implementation notes | ||
|
||
None | ||
|
||
## References | ||
|
||
* CERT-C: [ARR32-C: Ensure size arguments for variable length arrays are in a valid range](https://wiki.sei.cmu.edu/confluence/display/c) |
171 changes: 171 additions & 0 deletions
171
c/cert/src/rules/ARR32-C/VariableLengthArraySizeNotInValidRange.ql
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,171 @@ | ||
/** | ||
* @id c/cert/variable-length-array-size-not-in-valid-range | ||
* @name ARR32-C: Ensure size arguments for variable length arrays are in a valid range | ||
* @description A variable-length array size that is zero, negative, overflowed, wrapped around, or | ||
* excessively large may lead to undefined behaviour. | ||
* @kind problem | ||
* @precision high | ||
* @problem.severity error | ||
* @tags external/cert/id/arr32-c | ||
* correctness | ||
* security | ||
* external/cert/obligation/rule | ||
*/ | ||
|
||
import cpp | ||
import codingstandards.c.cert | ||
import codingstandards.cpp.Overflow | ||
|
||
/** | ||
* Gets the maximum size (in bytes) a variable-length array | ||
* should be to not be deemed excessively large persuant to this rule. | ||
* This value has been arbitrarily chosen to be 2^16 - 1 bytes. | ||
*/ | ||
private int maximumTotalVlaSize() { result = 65535 } | ||
|
||
/** | ||
* Gets the base type of a pointer or array type. In the case of an array of | ||
* arrays, the inner base type is returned. | ||
* | ||
* Copied from IncorrectPointerScalingCommon.qll. | ||
*/ | ||
private Type baseType(Type t) { | ||
( | ||
exists(PointerType dt | | ||
dt = t.getUnspecifiedType() and | ||
result = dt.getBaseType().getUnspecifiedType() | ||
) | ||
or | ||
exists(ArrayType at | | ||
at = t.getUnspecifiedType() and | ||
not at.getBaseType().getUnspecifiedType() instanceof ArrayType and | ||
result = at.getBaseType().getUnspecifiedType() | ||
) | ||
or | ||
exists(ArrayType at, ArrayType at2 | | ||
at = t.getUnspecifiedType() and | ||
at2 = at.getBaseType().getUnspecifiedType() and | ||
result = baseType(at2) | ||
) | ||
) and | ||
// Make sure that the type has a size and that it isn't ambiguous. | ||
strictcount(result.getSize()) = 1 | ||
} | ||
|
||
/** | ||
* The `SimpleRangeAnalysis` analysis over-zealously expands upper bounds of | ||
* `SubExpr`s to account for potential wrapping even when no wrapping can occur. | ||
* | ||
* This class represents a `SubExpr` that is safe from wrapping. | ||
*/ | ||
class SafeSubExprWithErroneouslyWrappedUpperBound extends SubExpr { | ||
SafeSubExprWithErroneouslyWrappedUpperBound() { | ||
lowerBound(this.getLeftOperand().getFullyConverted()) - | ||
upperBound(this.getRightOperand().getFullyConverted()) >= 0 and | ||
upperBound(this.getFullyConverted()) = exprMaxVal(this.getFullyConverted()) | ||
} | ||
|
||
/** | ||
* Gets the lower bound of the difference. | ||
*/ | ||
float getlowerBoundOfDifference() { | ||
result = | ||
lowerBound(this.getLeftOperand().getFullyConverted()) - | ||
upperBound(this.getRightOperand().getFullyConverted()) | ||
} | ||
} | ||
|
||
/** | ||
* Holds if `e` is an expression that is not in a valid range due to it | ||
* being partially or fully derived from an overflowing arithmetic operation. | ||
*/ | ||
predicate isExprTaintedByOverflowingExpr(Expr e) { | ||
exists(InterestingOverflowingOperation bop | | ||
// `bop` is not pre-checked to prevent overflow/wrapping | ||
not bop.hasValidPreCheck() and | ||
// and the destination is tainted by `bop` | ||
TaintTracking::localExprTaint(bop, e.getAChild*()) and | ||
// and there does not exist a post-wrapping-check before `e` | ||
not exists(GuardCondition gc | | ||
gc = bop.getAValidPostCheck() and | ||
gc.controls(e.getBasicBlock(), _) | ||
) | ||
) | ||
} | ||
|
||
predicate getVlaSizeExprBounds(Expr e, float lower, float upper) { | ||
lower = lowerBound(e) and | ||
upper = | ||
// upper is the smallest of either a `SubExpr` which flows to `e` and does | ||
// not wrap, or the upper bound of `e` derived from the range-analysis library | ||
min(float f | | ||
f = | ||
any(SafeSubExprWithErroneouslyWrappedUpperBound sub | | ||
DataFlow::localExprFlow(sub, e) | ||
| | ||
sub.getlowerBoundOfDifference() | ||
) or | ||
f = upperBound(e) | ||
) | ||
} | ||
|
||
/** | ||
* Holds if `e` is not bounded to a valid range, (0 .. maximumTotalVlaSize()], for | ||
* a element count of an individual variable-length array dimension. | ||
*/ | ||
predicate isVlaSizeExprOutOfRange(VlaDeclStmt vla, Expr e) { | ||
vla.getVlaDimensionStmt(_).getDimensionExpr() = e and | ||
exists(float lower, float upper | | ||
getVlaSizeExprBounds(e.getFullyConverted(), lower, upper) and | ||
( | ||
lower <= 0 | ||
or | ||
upper > maximumTotalVlaSize() / baseType(vla.getVariable().getType()).getSize() | ||
) | ||
) | ||
} | ||
|
||
/** | ||
* Returns the upper bound of `e.getFullyConverted()`. | ||
*/ | ||
float getVlaSizeExprUpperBound(Expr e) { getVlaSizeExprBounds(e.getFullyConverted(), _, result) } | ||
|
||
/** | ||
* Returns the upper bound of `vla`'s dimension expression at `index`. | ||
* | ||
* If `index` does not exist, then the result is `1`. | ||
*/ | ||
bindingset[index] | ||
private float getVlaSizeExprUpperBoundAtIndexOrOne(VlaDeclStmt vla, float index) { | ||
if vla.getNumberOfVlaDimensionStmts() > index | ||
then result = getVlaSizeExprUpperBound(vla.getVlaDimensionStmt(index).getDimensionExpr()) | ||
else result = 1 | ||
} | ||
|
||
predicate vlaupper = getVlaSizeExprUpperBoundAtIndexOrOne/2; | ||
|
||
/** | ||
* Gets the upper bound of the total size of `vla`. | ||
*/ | ||
float getTotalVlaSizeUpperBound(VlaDeclStmt vla) { | ||
result = | ||
vlaupper(vla, 0) * vlaupper(vla, 1) * vlaupper(vla, 2) * vlaupper(vla, 3) * vlaupper(vla, 4) * | ||
vlaupper(vla, 5) * vlaupper(vla, 6) * vlaupper(vla, 7) * vlaupper(vla, 8) * vlaupper(vla, 9) | ||
} | ||
|
||
from VlaDeclStmt vla, string message | ||
where | ||
not isExcluded(vla, InvalidMemory2Package::variableLengthArraySizeNotInValidRangeQuery()) and | ||
( | ||
if isExprTaintedByOverflowingExpr(vla.getVlaDimensionStmt(_).getDimensionExpr()) | ||
then message = "Variable-length array size derives from an overflowing or wrapping expression." | ||
else ( | ||
if isVlaSizeExprOutOfRange(vla, vla.getVlaDimensionStmt(_).getDimensionExpr()) | ||
then message = "Variable-length array dimension size may be in an invalid range." | ||
else ( | ||
getTotalVlaSizeUpperBound(vla) > maximumTotalVlaSize() and | ||
message = "Variable-length array total size may be excessively large." | ||
) | ||
) | ||
) | ||
select vla, message |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.