Skip to content

Implement Types Package #237

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 61 commits into from
Mar 29, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
61 commits
Select commit Hold shift + click to select a range
2dc3ba3
Initialize Types package
jeongsoolee09 Feb 24, 2023
d5259e2
Create test.c for RULE-12-5
jeongsoolee09 Feb 25, 2023
c6682eb
Remove file staged by mistake and really add test.c
jeongsoolee09 Feb 25, 2023
6b57f8d
Remove bogus case and make `test.c` compile
jeongsoolee09 Feb 27, 2023
405f28b
Remove bogus files
jeongsoolee09 Feb 27, 2023
d8cd0bf
Implement RULE-12-5
jeongsoolee09 Feb 27, 2023
3a3eba2
Remove bogus files for RULE-7-4
jeongsoolee09 Feb 27, 2023
3034493
Remove main
jeongsoolee09 Feb 28, 2023
25286ad
Add test.c for RULE-7-4
jeongsoolee09 Feb 28, 2023
14350d0
modified test.c for 7-4
jeongsoolee09 Feb 28, 2023
2ebcf85
Slim down test.c for 7-4
jeongsoolee09 Feb 28, 2023
16fe159
Draft of 7-4
jeongsoolee09 Feb 28, 2023
b51ac0e
Update .expected for 7-4
jeongsoolee09 Feb 28, 2023
ccf9f5f
Remove bogus files
jeongsoolee09 Feb 28, 2023
ccfeb06
Remove bogus file
jeongsoolee09 Feb 28, 2023
7e837dc
Add test cases for DIR-4-6
jeongsoolee09 Feb 28, 2023
87a0a3d
Draft of 4-6
jeongsoolee09 Mar 1, 2023
b1d08d3
Initialize INT34-C
jeongsoolee09 Mar 2, 2023
1b5c862
Prepare test cases for INT34
jeongsoolee09 Mar 2, 2023
3d30316
Implement INT34-C
jeongsoolee09 Mar 2, 2023
9ddb2c6
Draft for INT36-C
jeongsoolee09 Mar 3, 2023
0b242cb
Add test.c for INT36-C
jeongsoolee09 Mar 3, 2023
2c36364
Implement INT36-C
jeongsoolee09 Mar 3, 2023
20bc3ab
Some minor comment adjustments
jeongsoolee09 Mar 3, 2023
887c215
Add missing help query help file for INT36-c
jeongsoolee09 Mar 3, 2023
9e2af63
Merge branch 'main' into jeongsoolee09/Types
jeongsoolee09 Mar 3, 2023
c2ced98
Update select clause for 7-4
jeongsoolee09 Mar 4, 2023
f406729
Add an additional check to INT36-C
jeongsoolee09 Mar 6, 2023
2c1ea82
Minor comment stuff
jeongsoolee09 Mar 6, 2023
1408a85
Address minor things for Actions
jeongsoolee09 Mar 6, 2023
cb45556
Update queries and .expected for DIR-4-6
jeongsoolee09 Mar 6, 2023
f6488aa
Format query metadata
jeongsoolee09 Mar 6, 2023
aeb9b65
Factor out shared clauses to common
jeongsoolee09 Mar 6, 2023
a0a9aa1
Merge branch 'main' into jeongsoolee09/Types
jeongsoolee09 Mar 6, 2023
0f532e3
Update .expected for 7-4
jeongsoolee09 Mar 6, 2023
7617acc
Reinforce 7-4 to consider wchar_t
jeongsoolee09 Mar 21, 2023
3bec0e6
update .expected for RULE-7-4
jeongsoolee09 Mar 21, 2023
99a21b1
Checkpoint: INT34-C
jeongsoolee09 Mar 22, 2023
fb1fd83
Fix error in test of INT36-C
jeongsoolee09 Mar 22, 2023
3778724
Incorporate changes for INT36-C
jeongsoolee09 Mar 23, 2023
907e158
Finalize INT34-C
jeongsoolee09 Mar 24, 2023
c0b818c
Merge branch 'main' into jeongsoolee09/Types
jeongsoolee09 Mar 24, 2023
ec36beb
Update .expected for INT36-C
jeongsoolee09 Mar 24, 2023
0ec3fd6
Merge branch 'jeongsoolee09/Types' of github.com:github/codeql-coding…
jeongsoolee09 Mar 24, 2023
7de306d
Format test suites
jeongsoolee09 Mar 24, 2023
fbdbff1
Rename rule package to Types1
jeongsoolee09 Mar 24, 2023
7a6fb0b
Add missing metadata files
jeongsoolee09 Mar 24, 2023
08956e1
Add parameter name to INT34-C popcount
jeongsoolee09 Mar 24, 2023
97a33e4
Update .expected for INT34-C
jeongsoolee09 Mar 24, 2023
cc4a2d1
Merge branch 'main' into jeongsoolee09/Types
jeongsoolee09 Mar 24, 2023
09eab92
Merge branch 'main' into jeongsoolee09/Types
jeongsoolee09 Mar 27, 2023
37d59bb
Update DIR-4-6 to include size check for typedef
jeongsoolee09 Mar 27, 2023
2889a5d
Address inconsistency in rules.csv
jeongsoolee09 Mar 27, 2023
ea31308
Format test.c for DIR-4-6
jeongsoolee09 Mar 27, 2023
207d908
Tidy up overall
jeongsoolee09 Mar 28, 2023
f0023d6
Merge branch 'main' into jeongsoolee09/Types
jeongsoolee09 Mar 28, 2023
b79e1e8
INT34-C: Use fully converted type for precision
lcartey Mar 29, 2023
4e5e05a
INT34-C: Improve alert message.
lcartey Mar 29, 2023
9fc57bd
DIR-4-6: Only flag aliases of built-in numeric types.
lcartey Mar 29, 2023
93b9391
DIR-4-6: typedefs should be to numeric types
lcartey Mar 29, 2023
b33391d
Merge branch 'main' into jeongsoolee09/Types
lcartey Mar 29, 2023
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,216 @@
# INT34-C: Bit shift should not be done by a negative operand or an operand of greater-or-equal precision than that of another

This query implements the CERT-C rule INT34-C:

> Do not shift an expression by a negative number of bits or by greater than or equal to the number of bits that exist in the operand


## Description

Bitwise shifts include left-shift operations of the form *shift-expression* `<<` *additive-expression* and right-shift operations of the form *shift-expression* `>>` *additive-expression*. The standard integer promotions are first performed on the operands, each of which has an integer type. The type of the result is that of the promoted left operand. If the value of the right operand is negative or is greater than or equal to the width of the promoted left operand, the behavior is [undefined](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-undefinedbehavior). (See [undefined behavior 51](https://wiki.sei.cmu.edu/confluence/display/c/CC.+Undefined+Behavior#CC.UndefinedBehavior-ub_51).)

Do not shift an expression by a negative number of bits or by a number greater than or equal to the *precision* of the promoted left operand. The precision of an integer type is the number of bits it uses to represent values, excluding any sign and padding bits. For unsigned integer types, the width and the precision are the same; whereas for signed integer types, the width is one greater than the precision. This rule uses precision instead of width because, in almost every case, an attempt to shift by a number of bits greater than or equal to the precision of the operand indicates a bug (logic error). A logic error is different from overflow, in which there is simply a representational deficiency. In general, shifts should be performed only on unsigned operands. (See [INT13-C. Use bitwise operators only on unsigned operands](https://wiki.sei.cmu.edu/confluence/display/c/INT13-C.+Use+bitwise+operators+only+on+unsigned+operands).)

## Noncompliant Code Example (Left Shift, Unsigned Type)

The result of `E1 << E2` is `E1` left-shifted `E2` bit positions; vacated bits are filled with zeros. The following diagram illustrates the left-shift operation.

![](ShiftLeft.JPG)

According to the C Standard, if `E1` has an unsigned type, the value of the result is `E1` \* `2``<sup>E2</sup>`, reduced modulo 1 more than the maximum value representable in the result type.

This noncompliant code example fails to ensure that the right operand is less than the precision of the promoted left operand:

```cpp
void func(unsigned int ui_a, unsigned int ui_b) {
unsigned int uresult = ui_a << ui_b;
/* ... */
}
```

## Compliant Solution (Left Shift, Unsigned Type)

This compliant solution eliminates the possibility of shifting by greater than or equal to the number of bits that exist in the precision of the left operand:

```cpp
#include <limits.h>
#include <stddef.h>
#include <inttypes.h>

extern size_t popcount(uintmax_t);
#define PRECISION(x) popcount(x)

void func(unsigned int ui_a, unsigned int ui_b) {
unsigned int uresult = 0;
if (ui_b >= PRECISION(UINT_MAX)) {
/* Handle error */
} else {
uresult = ui_a << ui_b;
}
/* ... */
}
```
The `PRECISION()` macro and `popcount()` function provide the correct precision for any integer type. (See [INT35-C. Use correct integer precisions](https://wiki.sei.cmu.edu/confluence/display/c/INT35-C.+Use+correct+integer+precisions).)

Modulo behavior resulting from left-shifting an unsigned integer type is permitted by exception INT30-EX3 to [INT30-C. Ensure that unsigned integer operations do not wrap](https://wiki.sei.cmu.edu/confluence/display/c/INT30-C.+Ensure+that+unsigned+integer+operations+do+not+wrap).

## Noncompliant Code Example (Left Shift, Signed Type)

The result of `E1 << E2` is `E1` left-shifted `E2` bit positions; vacated bits are filled with zeros. If `E1` has a signed type and nonnegative value, and `E1` \* `2``<sup>E2</sup>` is representable in the result type, then that is the resulting value; otherwise, the behavior is undefined.

This noncompliant code example fails to ensure that left and right operands have nonnegative values and that the right operand is less than the precision of the promoted left operand. This example does check for signed integer overflow in compliance with [INT32-C. Ensure that operations on signed integers do not result in overflow](https://wiki.sei.cmu.edu/confluence/display/c/INT32-C.+Ensure+that+operations+on+signed+integers+do+not+result+in+overflow).

```cpp
#include <limits.h>
#include <stddef.h>
#include <inttypes.h>

void func(signed long si_a, signed long si_b) {
signed long result;
if (si_a > (LONG_MAX >> si_b)) {
/* Handle error */
} else {
result = si_a << si_b;
}
/* ... */
}
```
Shift operators and other bitwise operators should be used only with unsigned integer operands in accordance with [INT13-C. Use bitwise operators only on unsigned operands](https://wiki.sei.cmu.edu/confluence/display/c/INT13-C.+Use+bitwise+operators+only+on+unsigned+operands).

## Compliant Solution (Left Shift, Signed Type)

In addition to the check for overflow, this compliant solution ensures that both the left and right operands have nonnegative values and that the right operand is less than the precision of the promoted left operand:

```cpp
#include <limits.h>
#include <stddef.h>
#include <inttypes.h>

extern size_t popcount(uintmax_t);
#define PRECISION(x) popcount(x)

void func(signed long si_a, signed long si_b) {
signed long result;
if ((si_a < 0) || (si_b < 0) ||
(si_b >= PRECISION(ULONG_MAX)) ||
(si_a > (LONG_MAX >> si_b))) {
/* Handle error */
} else {
result = si_a << si_b;
}
/* ... */
}

```
Noncompliant Code Example (Right Shift)

The result of `E1 >> E2` is `E1` right-shifted `E2` bit positions. If `E1` has an unsigned type or if `E1` has a signed type and a nonnegative value, the value of the result is the integral part of the quotient of `E1` / `2``<sup>E2</sup>`. If `E1` has a signed type and a negative value, the resulting value is [implementation-defined](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-implementation-definedbehavior) and can be either an arithmetic (signed) shift

![](ShiftRight.JPG)

or a logical (unsigned) shift

![](LogicalShiftRight.JPG)

This noncompliant code example fails to test whether the right operand is greater than or equal to the precision of the promoted left operand, allowing undefined behavior:

```cpp
void func(unsigned int ui_a, unsigned int ui_b) {
unsigned int uresult = ui_a >> ui_b;
/* ... */
}
```
When working with signed operands, making assumptions about whether a right shift is implemented as an arithmetic (signed) shift or a logical (unsigned) shift can also lead to [vulnerabilities](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-vulnerability). (See [INT13-C. Use bitwise operators only on unsigned operands](https://wiki.sei.cmu.edu/confluence/display/c/INT13-C.+Use+bitwise+operators+only+on+unsigned+operands).)

## Compliant Solution (Right Shift)

This compliant solution eliminates the possibility of shifting by greater than or equal to the number of bits that exist in the precision of the left operand:

```cpp
#include <limits.h>
#include <stddef.h>
#include <inttypes.h>

extern size_t popcount(uintmax_t);
#define PRECISION(x) popcount(x)

void func(unsigned int ui_a, unsigned int ui_b) {
unsigned int uresult = 0;
if (ui_b >= PRECISION(UINT_MAX)) {
/* Handle error */
} else {
uresult = ui_a >> ui_b;
}
/* ... */
}
```
**Implementation Details**

GCC has no options to handle shifts by negative amounts or by amounts outside the width of the type predictably or to trap on them; they are always treated as undefined. Processors may reduce the shift amount modulo the width of the type. For example, 32-bit right shifts are implemented using the following instruction on x86-32:

```cpp
sarl %cl, %eax

```
The `sarl` instruction takes a bit mask of the least significant 5 bits from `%cl` to produce a value in the range \[0, 31\] and then shift `%eax` that many bits:

```cpp
// 64-bit right shifts on IA-32 platforms become
shrdl %edx, %eax
sarl %cl, %edx

```
where `%eax` stores the least significant bits in the doubleword to be shifted, and `%edx` stores the most significant bits.

## Risk Assessment

Although shifting a negative number of bits or shifting a number of bits greater than or equal to the width of the promoted left operand is undefined behavior in C, the risk is generally low because processors frequently reduce the shift amount modulo the width of the type.

<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> INT34-C </td> <td> Low </td> <td> Unlikely </td> <td> Medium </td> <td> <strong>P2</strong> </td> <td> <strong>L3</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> Astrée </a> </td> <td> 22.04 </td> <td> <strong>precision-shift-width</strong> <strong>precision-shift-width-constant</strong> </td> <td> Fully checked </td> </tr> <tr> <td> <a> Axivion Bauhaus Suite </a> </td> <td> 7.2.0 </td> <td> <strong>CertC-INT34</strong> </td> <td> Can detect shifts by a negative or an excessive number of bits and right shifts on negative values. </td> </tr> <tr> <td> <a> CodeSonar </a> </td> <td> 7.2p0 </td> <td> <strong>LANG.ARITH.BIGSHIFT</strong> <strong>LANG.ARITH.NEGSHIFT</strong> </td> <td> Shift amount exceeds bit width Negative shift amount </td> </tr> <tr> <td> <a> Compass/ROSE </a> </td> <td> </td> <td> </td> <td> Can detect violations of this rule. Unsigned operands are detected when checking for <a> INT13-C. Use bitwise operators only on unsigned operands </a> </td> </tr> <tr> <td> <a> Coverity </a> </td> <td> 2017.07 </td> <td> <strong>BAD_SHIFT</strong> </td> <td> Implemented </td> </tr> <tr> <td> <a> Cppcheck </a> </td> <td> 1.66 </td> <td> <strong>shiftNegative, shiftTooManyBits</strong> </td> <td> Context sensitive analysis Warns whenever Cppcheck sees a negative shift for a POD expression (The warning for shifting too many bits is written only if Cppcheck has sufficient type information and you use <code>--platform</code> to specify the sizes of the standard types.) </td> </tr> <tr> <td> <a> ECLAIR </a> </td> <td> 1.2 </td> <td> <strong>CC2.INT34</strong> </td> <td> Partially implemented </td> </tr> <tr> <td> <a> Helix QAC </a> </td> <td> 2022.4 </td> <td> <strong>C0499, C2790, </strong> <strong>C++2790, C++3003</strong> <strong>DF2791, DF2792, DF2793</strong> </td> <td> </td> </tr> <tr> <td> <a> Klocwork </a> </td> <td> 2022.4 </td> <td> <strong>MISRA.SHIFT.RANGE.2012</strong> </td> <td> </td> </tr> <tr> <td> <a> LDRA tool suite </a> </td> <td> 9.7.1 </td> <td> <strong>51 S, 403 S, 479 S</strong> </td> <td> Partially implemented </td> </tr> <tr> <td> <a> Parasoft C/C++test </a> </td> <td> 2022.2 </td> <td> <strong>CERT_C-INT34-a</strong> </td> <td> Avoid incorrect shift operations </td> </tr> <tr> <td> <a> Polyspace Bug Finder </a> </td> <td> R2022b </td> <td> <a> CERT C: Rule INT34-C </a> </td> <td> Checks for: Shift of a negative valuehift of a negative value, shift operation overflowhift operation overflow. Rule partially covered. </td> </tr> <tr> <td> <a> PRQA QA-C </a> </td> <td> 9.7 </td> <td> <strong>0499, 2790 \[C\], 2791 \[D\], 2792 \[A\], 2793 \[S\]</strong> </td> <td> Partially implemented </td> </tr> <tr> <td> <a> PRQA QA-C++ </a> </td> <td> 4.4 </td> <td> <strong>2791, 2792, 2793, 3003, 3321, 3322</strong> </td> <td> </td> </tr> <tr> <td> <a> PVS-Studio </a> </td> <td> 7.23 </td> <td> <a> V610 </a> </td> <td> </td> </tr> <tr> <td> <a> RuleChecker </a> </td> <td> 22.04 </td> <td> <strong>precision-shift-width-constant</strong> </td> <td> Partially checked </td> </tr> <tr> <td> <a> TrustInSoft Analyzer </a> </td> <td> 1.38 </td> <td> <strong>shift</strong> </td> <td> Exhaustively verified (see <a> one compliant and one non-compliant example </a> ). </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+INT34-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 </a> </td> <td> <a> INT13-C. Use bitwise operators only on unsigned operands </a> </td> <td> Prior to 2018-01-12: CERT: Unspecified Relationship </td> </tr> <tr> <td> <a> CERT C </a> </td> <td> <a> INT35-C. Use correct integer precisions </a> </td> <td> Prior to 2018-01-12: CERT: Unspecified Relationship </td> </tr> <tr> <td> <a> CERT C </a> </td> <td> <a> INT32-C. Ensure that operations on signed integers do not result in overflow </a> </td> <td> Prior to 2018-01-12: CERT: Unspecified Relationship </td> </tr> <tr> <td> <a> ISO/IEC TR 24772:2013 </a> </td> <td> Arithmetic Wrap-Around Error \[FIF\] </td> <td> Prior to 2018-01-12: CERT: Unspecified Relationship </td> </tr> <tr> <td> <a> CWE 2.11 </a> </td> <td> <a> CWE-682 </a> </td> <td> 2017-07-07: CERT: Rule subset of CWE </td> </tr> <tr> <td> <a> CWE 2.11 </a> </td> <td> <a> CWE-758 </a> </td> <td> 2017-07-07: 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-758 and INT34-C**

Independent( INT34-C, INT36-C, MEM30-C, MSC37-C, FLP32-C, EXP33-C, EXP30-C, ERR34-C, ARR32-C)

CWE-758 = Union( INT34-C, list) where list =

* Undefined behavior that results from anything other than incorrect bit shifting
**CWE-682 and INT34-C**

Independent( INT34-C, FLP32-C, INT33-C) CWE-682 = Union( INT34-C, list) where list =

* Incorrect calculations that do not involve out-of-range bit shifts

## Bibliography

<table> <tbody> <tr> <td> \[ <a> C99 Rationale 2003 </a> \] </td> <td> 6.5.7, "Bitwise Shift Operators" </td> </tr> <tr> <td> \[ <a> Dowd 2006 </a> \] </td> <td> Chapter 6, "C Language Issues" </td> </tr> <tr> <td> \[ <a> Seacord 2013b </a> \] </td> <td> Chapter 5, "Integer Security" </td> </tr> <tr> <td> \[ <a> Viega 2005 </a> \] </td> <td> Section 5.2.7, "Integer Overflow" </td> </tr> </tbody> </table>


## Implementation notes

None

## References

* CERT-C: [INT34-C: Do not shift an expression by a negative number of bits or by greater than or equal to the number of bits that exist in the operand](https://wiki.sei.cmu.edu/confluence/display/c)
Original file line number Diff line number Diff line change
@@ -0,0 +1,105 @@
/**
* @id c/cert/expr-shiftedby-negative-or-greater-precision-operand
* @name INT34-C: Bit shift should not be done by a negative operand or an operand of greater-or-equal precision than that of another
* @description Shifting an expression by an operand that is negative or of precision greater or
* equal to that or the another causes representational error.
* @kind problem
* @precision very-high
* @problem.severity error
* @tags external/cert/id/int34-c
* external/cert/obligation/rule
*/

import cpp
import codingstandards.c.cert
import semmle.code.cpp.rangeanalysis.SimpleRangeAnalysis
import semmle.code.cpp.ir.internal.ASTValueNumbering
import semmle.code.cpp.controlflow.Guards

/*
* Precision predicate based on a sample implementation from
* https://wiki.sei.cmu.edu/confluence/display/c/INT35-C.+Use+correct+integer+precisions
*/

/**
* A function whose name is suggestive that it counts the number of bits set.
*/
class PopCount extends Function {
PopCount() { this.getName().toLowerCase().matches("%popc%nt%") }
}

/**
* A macro which is suggestive that it is used to determine the precision of an integer.
*/
class PrecisionMacro extends Macro {
PrecisionMacro() { this.getName().toLowerCase().matches("precision") }
}

class LiteralZero extends Literal {
LiteralZero() { this.getValue() = "0" }
}

class BitShiftExpr extends BinaryBitwiseOperation {
BitShiftExpr() {
this instanceof LShiftExpr or
this instanceof RShiftExpr
}
}

int getPrecision(IntegralType type) {
type.isExplicitlyUnsigned() and result = type.getSize() * 8
or
type.isExplicitlySigned() and result = type.getSize() * 8 - 1
}

predicate isForbiddenShiftExpr(BitShiftExpr shift, string message) {
(
(
getPrecision(shift.getLeftOperand().getExplicitlyConverted().getUnderlyingType()) <=
upperBound(shift.getRightOperand()) and
message =
"The operand " + shift.getLeftOperand() + " is shifted by an expression " +
shift.getRightOperand() + " whose upper bound (" + upperBound(shift.getRightOperand()) +
") is greater than or equal to the precision."
or
lowerBound(shift.getRightOperand()) < 0 and
message =
"The operand " + shift.getLeftOperand() + " is shifted by an expression " +
shift.getRightOperand() + " which may be negative."
) and
/*
* Shift statement is not at a basic block where
* `shift_rhs < PRECISION(...)` is ensured
*/

not exists(GuardCondition gc, BasicBlock block, Expr precisionCall, Expr lTLhs |
block = shift.getBasicBlock() and
(
precisionCall.(FunctionCall).getTarget() instanceof PopCount
or
precisionCall = any(PrecisionMacro pm).getAnInvocation().getExpr()
)
|
globalValueNumber(lTLhs) = globalValueNumber(shift.getRightOperand()) and
gc.ensuresLt(lTLhs, precisionCall, 0, block, true)
) and
/*
* Shift statement is not at a basic block where
* `shift_rhs < 0` is ensured
*/

not exists(GuardCondition gc, BasicBlock block, Expr literalZero, Expr lTLhs |
block = shift.getBasicBlock() and
literalZero instanceof LiteralZero
|
globalValueNumber(lTLhs) = globalValueNumber(shift.getRightOperand()) and
gc.ensuresLt(lTLhs, literalZero, 0, block, true)
)
)
}

from BinaryBitwiseOperation badShift, string message
where
not isExcluded(badShift, Types1Package::exprShiftedbyNegativeOrGreaterPrecisionOperandQuery()) and
isForbiddenShiftExpr(badShift, message)
select badShift, message
Binary file added c/cert/src/rules/INT34-C/LogicalShiftRight.JPG
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added c/cert/src/rules/INT34-C/ShiftLeft.JPG
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added c/cert/src/rules/INT34-C/ShiftRight.JPG
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading