Skip to content

Commit 59d9565

Browse files
committed
Declarations2: add rule DCL38-C and omit RULE-17-6 from csv
1 parent 36a4e3f commit 59d9565

File tree

8 files changed

+236
-3
lines changed

8 files changed

+236
-3
lines changed
Lines changed: 130 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,130 @@
1+
# DCL38-C: Use the correct syntax when declaring a flexible array member
2+
3+
This query implements the CERT-C rule DCL38-C:
4+
5+
> Use the correct syntax when declaring a flexible array member
6+
7+
8+
9+
## Description
10+
11+
Flexible array members are a special type of array in which the last element of a structure with more than one named member has an incomplete array type; that is, the size of the array is not specified explicitly within the structure. This "struct hack" was widely used in practice and supported by a variety of compilers. Consequently, a variety of different syntaxes have been used for declaring flexible array members. For conforming C implementations, use the syntax guaranteed to be valid by the C Standard.
12+
13+
Flexible array members are defined in the C Standard, 6.7.2.1, paragraph 18 \[[ISO/IEC 9899:2011](https://wiki.sei.cmu.edu/confluence/display/c/AA.+Bibliography#AA.Bibliography-ISO-IEC9899-2011)\], as follows:
14+
15+
> As a special case, the last element of a structure with more than one named member may have an incomplete array type; this is called a *flexible array member*. In most situations, the flexible array member is ignored. In particular, the size of the structure is as if the flexible array member were omitted except that it may have more trailing padding than the omission would imply. However, when a `**.**`(or `**->**`) operator has a left operand that is (a pointer to) a structure with a flexible array member and the right operand names that member, it behaves as if that member were replaced with the longest array (with the same element type) that would not make the structure larger than the object being accessed; the offset of the array shall remain that of the flexible array member, even if this would differ from that of the replacement array. If this array would have no elements, it behaves as if it had one element but the behavior is undefined if any attempt is made to access that element or to generate a pointer one past it.
16+
17+
18+
Structures with a flexible array member can be used to produce code with defined behavior. However, some restrictions apply:
19+
20+
1. The incomplete array type *must* be the last element within the structure.
21+
1. There cannot be an array of structures that contain a flexible array member.
22+
1. Structures that contain a flexible array member cannot be used as a member of another structure.
23+
1. The structure must contain at least one named member in addition to the flexible array member.
24+
25+
## Noncompliant Code Example
26+
27+
Before the introduction of flexible array members in the C Standard, structures with a one-element array as the final member were used to achieve similar functionality. This noncompliant code example illustrates how `struct flexArrayStruct` is declared in this case.
28+
29+
This noncompliant code example attempts to allocate a flexible array-like member with a one-element array as the final member. When the structure is instantiated, the size computed for `malloc()` is modified to account for the actual size of the dynamic array.
30+
31+
```cpp
32+
#include <stdlib.h>
33+
34+
struct flexArrayStruct {
35+
int num;
36+
int data[1];
37+
};
38+
39+
void func(size_t array_size) {
40+
/* Space is allocated for the struct */
41+
struct flexArrayStruct *structP
42+
= (struct flexArrayStruct *)
43+
malloc(sizeof(struct flexArrayStruct)
44+
+ sizeof(int) * (array_size - 1));
45+
if (structP == NULL) {
46+
/* Handle malloc failure */
47+
}
48+
49+
structP->num = array_size;
50+
51+
/*
52+
* Access data[] as if it had been allocated
53+
* as data[array_size].
54+
*/
55+
for (size_t i = 0; i < array_size; ++i) {
56+
structP->data[i] = 1;
57+
}
58+
}
59+
```
60+
This example has [undefined behavior](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-undefinedbehavior) when accessing any element other than the first element of the `data` array. (See the C Standard, 6.5.6.) Consequently, the compiler can generate code that does not return the expected value when accessing the second element of data.
61+
62+
This approach may be the only alternative for compilers that do not yet implement the standard C syntax.
63+
64+
## Compliant Solution
65+
66+
This compliant solution uses a flexible array member to achieve a dynamically sized structure:
67+
68+
```cpp
69+
#include <stdlib.h>
70+
71+
struct flexArrayStruct{
72+
int num;
73+
int data[];
74+
};
75+
76+
void func(size_t array_size) {
77+
/* Space is allocated for the struct */
78+
struct flexArrayStruct *structP
79+
= (struct flexArrayStruct *)
80+
malloc(sizeof(struct flexArrayStruct)
81+
+ sizeof(int) * array_size);
82+
if (structP == NULL) {
83+
/* Handle malloc failure */
84+
}
85+
86+
structP->num = array_size;
87+
88+
/*
89+
* Access data[] as if it had been allocated
90+
* as data[array_size].
91+
*/
92+
for (size_t i = 0; i < array_size; ++i) {
93+
structP->data[i] = 1;
94+
}
95+
}
96+
```
97+
This compliant solution allows the structure to be treated as if its member `data[]` was declared to be `data[array_size]` in a manner that conforms to the C Standard.
98+
99+
## Risk Assessment
100+
101+
Failing to use the correct syntax when declaring a flexible array member can result in [undefined behavior](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-undefinedbehavior), although the incorrect syntax will work on most implementations.
102+
103+
<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> DCL38-C </td> <td> Low </td> <td> Unlikely </td> <td> Low </td> <td> <strong>P3</strong> </td> <td> <strong>L3</strong> </td> </tr> </tbody> </table>
104+
105+
106+
## Automated Detection
107+
108+
<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>array_out_of_bounds</strong> </td> <td> Supported Astrée reports all out-of-bounds array access. </td> </tr> <tr> <td> <a> Axivion Bauhaus Suite </a> </td> <td> 7.2.0 </td> <td> <strong>CertC-DCL38</strong> </td> <td> Detects if the final member of struct which is declared as an array of small bound, is used as a flexible array member. </td> </tr> <tr> <td> <a> Compass/ROSE </a> </td> <td> </td> <td> </td> <td> Can detect some violations of this rule. In particular, it warns if the last element of a <code>struct</code> is an array with a small index (0 or 1) </td> </tr> <tr> <td> <a> Helix QAC </a> </td> <td> 2022.2 </td> <td> <strong>C1037, C1039</strong> </td> <td> </td> </tr> <tr> <td> <a> Klocwork </a> </td> <td> 2022.2 </td> <td> <strong>CERT.STRUCT.FLEXIBLE_ARRAY_MEMBER</strong> </td> <td> </td> </tr> <tr> <td> <a> LDRA tool suite </a> </td> <td> 9.7.1 </td> <td> <strong>648 S</strong> </td> <td> Fully implemented </td> </tr> <tr> <td> <a> Parasoft C/C++test </a> </td> <td> 2022.1 </td> <td> <strong>CERT_C-DCL38-a</strong> </td> <td> The final member of a structure should not be an array of size '0' or '1' </td> </tr> <tr> <td> <a> PC-lint Plus </a> </td> <td> 1.4 </td> <td> <strong>9040</strong> </td> <td> Fully supported </td> </tr> <tr> <td> <a> Polyspace Bug Finder </a> </td> <td> R2022a </td> <td> <a> CERT C: Rule DCL38-C </a> </td> <td> Checks for incorrect syntax of flexible array member size (rule fully covered) </td> </tr> <tr> <td> <a> PRQA QA-C </a> </td> <td> 9.7 </td> <td> <strong>1037 1039</strong> </td> <td> </td> </tr> <tr> <td> <a> TrustInSoft Analyzer </a> </td> <td> 1.38 </td> <td> <strong>index_bound</strong> </td> <td> Exhaustively detects out-of-bounds array access (see <a> the compliant and the non-compliant example </a> ). </td> </tr> </tbody> </table>
109+
110+
111+
## Related Vulnerabilities
112+
113+
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+DCL38-C).
114+
115+
## Related Guidelines
116+
117+
This rule supplements [MEM33-C. Allocate and copy structures containing a flexible array member dynamically](https://wiki.sei.cmu.edu/confluence/display/c/MEM33-C.++Allocate+and+copy+structures+containing+a+flexible+array+member+dynamically)
118+
119+
## Bibliography
120+
121+
<table> <tbody> <tr> <td> \[ <a> ISO/IEC 9899:2011 </a> \] </td> <td> 6.5.6, "Additive Operators" 6.7.2.1, "Structure and Union Specifiers" </td> </tr> <tr> <td> \[ <a> McCluskey 2001 </a> \] </td> <td> " <a> Flexible Array Members and Designators in C9X </a> " </td> </tr> </tbody> </table>
122+
123+
124+
## Implementation notes
125+
126+
None
127+
128+
## References
129+
130+
* CERT-C: [DCL38-C: Use the correct syntax when declaring a flexible array member](https://wiki.sei.cmu.edu/confluence/display/c)
Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
/**
2+
* @id c/cert/declaring-a-flexible-array-member
3+
* @name DCL38-C: Use the correct syntax when declaring a flexible array member
4+
* @description Structures with flexible array members can be declared in ways that will lead to
5+
* undefined behaviour.
6+
* @kind problem
7+
* @precision very-high
8+
* @problem.severity error
9+
* @tags external/cert/id/dcl38-c
10+
* correctness
11+
* maintainability
12+
* readability
13+
* external/cert/obligation/rule
14+
*/
15+
16+
import cpp
17+
import codingstandards.c.cert
18+
19+
/**
20+
* A member with the type array that is last in a struct
21+
* includes any sized array (either specified or not)
22+
*/
23+
class FlexibleArrayMember extends MemberVariable {
24+
Struct s;
25+
26+
FlexibleArrayMember() {
27+
this.getType() instanceof ArrayType and
28+
this.getDeclaringType() = s and
29+
not exists(int i, int j |
30+
s.getAMember(i) = this and
31+
exists(s.getAMember(j)) and
32+
j > i
33+
)
34+
}
35+
}
36+
37+
from VariableDeclarationEntry m, ArrayType a
38+
where
39+
not isExcluded(m, Declarations2Package::declaringAFlexibleArrayMemberQuery()) and
40+
m.getType() = a and
41+
m.getVariable() instanceof FlexibleArrayMember and
42+
a.getArraySize() = 1
43+
select m, "Incorrect syntax used for declaring this flexible array member."
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
| test.c:3:7:3:7 | definition of b | Incorrect syntax used for declaring this flexible array member. |
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
rules/DCL38-C/DeclaringAFlexibleArrayMember.ql

c/cert/test/rules/DCL38-C/test.c

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
struct s {
2+
int a;
3+
int b[1]; // NON_COMPLIANT
4+
};
5+
6+
struct s1 {
7+
int a;
8+
int b[]; // COMPLIANT
9+
};
10+
11+
struct s2 {
12+
int a;
13+
int b[2]; // COMPLIANT
14+
};
15+
16+
struct s3 {
17+
int a;
18+
int b[1]; // COMPLIANT
19+
int a1;
20+
};

cpp/common/src/codingstandards/cpp/exclusions/c/Declarations2.qll

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,19 @@ import cpp
33
import RuleMetadata
44
import codingstandards.cpp.exclusions.RuleMetadata
55

6-
newtype Declarations2Query = TVariablesInsideSwitchStatementQuery()
6+
newtype Declarations2Query =
7+
TDeclaringAFlexibleArrayMemberQuery() or
8+
TVariablesInsideSwitchStatementQuery()
79

810
predicate isDeclarations2QueryMetadata(Query query, string queryId, string ruleId) {
11+
query =
12+
// `Query` instance for the `declaringAFlexibleArrayMember` query
13+
Declarations2Package::declaringAFlexibleArrayMemberQuery() and
14+
queryId =
15+
// `@id` for the `declaringAFlexibleArrayMember` query
16+
"c/cert/declaring-a-flexible-array-member" and
17+
ruleId = "DCL38-C"
18+
or
919
query =
1020
// `Query` instance for the `variablesInsideSwitchStatement` query
1121
Declarations2Package::variablesInsideSwitchStatementQuery() and
@@ -16,6 +26,13 @@ predicate isDeclarations2QueryMetadata(Query query, string queryId, string ruleI
1626
}
1727

1828
module Declarations2Package {
29+
Query declaringAFlexibleArrayMemberQuery() {
30+
//autogenerate `Query` type
31+
result =
32+
// `Query` type for `declaringAFlexibleArrayMember` query
33+
TQueryC(TDeclarations2PackageQuery(TDeclaringAFlexibleArrayMemberQuery()))
34+
}
35+
1936
Query variablesInsideSwitchStatementQuery() {
2037
//autogenerate `Query` type
2138
result =

rule_packages/c/Declarations2.json

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,26 @@
11
{
22
"CERT-C": {
3+
"DCL38-C": {
4+
"properties": {
5+
"obligation": "rule"
6+
},
7+
"queries": [
8+
{
9+
"description": "Structures with flexible array members can be declared in ways that will lead to undefined behaviour.",
10+
"kind": "problem",
11+
"name": "Use the correct syntax when declaring a flexible array member",
12+
"precision": "very-high",
13+
"severity": "error",
14+
"short_name": "DeclaringAFlexibleArrayMember",
15+
"tags": [
16+
"correctness",
17+
"maintainability",
18+
"readability"
19+
]
20+
}
21+
],
22+
"title": "Use the correct syntax when declaring a flexible array member"
23+
},
324
"DCL41-C": {
425
"properties": {
526
"obligation": "rule"

rules.csv

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -502,7 +502,7 @@ c,CERT-C,DCL30-C,Yes,Rule,,,Declare objects with appropriate storage durations,,
502502
c,CERT-C,DCL31-C,Yes,Rule,,,Declare identifiers before using them,,Declarations1,Medium,
503503
c,CERT-C,DCL36-C,Yes,Rule,,,Do not declare an identifier with conflicting linkage classifications,,Declarations,Medium,
504504
c,CERT-C,DCL37-C,Yes,Rule,,,Do not declare or define a reserved identifier,,Declarations1,Easy,
505-
c,CERT-C,DCL38-C,Yes,Rule,,,Use the correct syntax when declaring a flexible array member,,Declarations,Easy,
505+
c,CERT-C,DCL38-C,Yes,Rule,,,Use the correct syntax when declaring a flexible array member,,Declarations2,Easy,
506506
c,CERT-C,DCL39-C,Yes,Rule,,,Avoid information leakage when passing a structure across a trust boundary,,Declarations,Hard,
507507
c,CERT-C,DCL40-C,Yes,Rule,,,Do not create incompatible declarations of the same function or object,,Declarations,Hard,
508508
c,CERT-C,DCL41-C,Yes,Rule,,,Do not declare variables inside a switch statement before the first case label,,Declarations2,Medium,
@@ -716,7 +716,7 @@ c,MISRA-C-2012,RULE-17-2,Yes,Required,,,"Functions shall not call themselves, ei
716716
c,MISRA-C-2012,RULE-17-3,Yes,Mandatory,,,A function shall not be declared implicitly,,Declarations,Medium,
717717
c,MISRA-C-2012,RULE-17-4,Yes,Mandatory,,,All exit paths from a function with non-void return type shall have an explicit return statement with an expression,MSC52-CPP,Statements,Medium,
718718
c,MISRA-C-2012,RULE-17-5,Yes,Advisory,,,The function argument corresponding to a parameter declared to have an array type shall have an appropriate number of elements,,Contracts,Hard,
719-
c,MISRA-C-2012,RULE-17-6,Yes,Mandatory,,,The declaration of an array parameter shall not contain the static keyword between the [ ],,Declarations,Easy,
719+
c,MISRA-C-2012,RULE-17-6,No,Mandatory,,,The declaration of an array parameter shall not contain the static keyword between the [ ],,,,
720720
c,MISRA-C-2012,RULE-17-7,Yes,Required,,,The value returned by a function having non-void return type shall be used,A0-1-2,Contracts,Import,
721721
c,MISRA-C-2012,RULE-17-8,Yes,Advisory,,,A function parameter should not be modified,,SideEffects2,Medium,
722722
c,MISRA-C-2012,RULE-18-1,Yes,Required,,,A pointer resulting from arithmetic on a pointer operand shall address an element of the same array as that pointer operand,M5-0-16,Pointers1,Import,

0 commit comments

Comments
 (0)