...
- The alignment of bit-fields in the storage unit . For (for example, the bit-fields may be allocated from the high end or the low end of the storage unit.)
- Whether or not bit-fields can overlap a storage unit boundary.
Consequently, it is impossible to write portable safe code that makes assumptions regarding the layout of bit-field structure members.
...
Code Block |
---|
|
struct bf {
unsigned int m1 : 8;
unsigned int m2 : 8;
unsigned int m3 : 8;
unsigned int m4 : 8;
}; /* 32 bits total */
void function() {
struct bf data;
unsigned char *ptr;
data.m1 = 0;
data.m2 = 0;
data.m3 = 0;
data.m4 = 0;
ptr = (unsigned char *)&data;
(*ptr)++; /* canCan increment data.m1 or data.m4 */
}
|
...
This compliant solution is explicit in which fields it modifies.:
Code Block |
---|
|
struct bf {
unsigned int m1 : 8;
unsigned int m2 : 8;
unsigned int m3 : 8;
unsigned int m4 : 8;
}; /* 32 bits total */
void function() {
struct bf data;
data.m1 = 0;
data.m2 = 0;
data.m3 = 0;
data.m4 = 0;
data.m1++;
}
|
Noncompliant Code Example (Bit-Field Overlap)
In the following this noncompliant code example, assuming 8 bits to a byte, if bit-fields of 6 and 4 bits are declared, is each bit-field contained within a byte, or are the bit-fields split across multiple bytes?
Code Block |
---|
|
struct bf {
unsigned int m1 : 6;
unsigned int m2 : 4;
};
void function() {
unsigned char *ptr;
struct bf data;
data.m1 = 0;
data.m2 = 0;
ptr = (unsigned char *)&data;
ptr++;
*ptr += 1; /* whatWhat does this increment? */
}
|
...
This compliant solution is explicit in which fields it modifies.:
Code Block |
---|
|
struct bf {
unsigned int m1 : 6;
unsigned int m2 : 4;
};
void function() {
struct bf data;
data.m1 = 0;
data.m2 = 0;
data.m2 += 1;
}
|
...
Making invalid assumptions about the type of type-cast data, especially bit-fields, can result in unexpected data values.
Recommendation | Severity | Likelihood | Remediation Cost | Priority | Level |
---|
EXP11-C |
mediumprobablemediumAutomated Detection
Tool | Version | Checker | Description |
---|
Astrée | |
| Supported: Astrée reports runtime errors resulting from invalid assumptions. |
Compass/ROSE |
| |
|
| Can detect violations of this recommendation. Specifically, it reports violations if |
a pointer - A pointer to one object is type cast to the pointer of a different object
|
.the - The pointed-to object of the (type cast) pointer is then modified arithmetically
|
.LDRA tool suiteLDRALDRA94 S 95 S | Fully implemented. | PRQA QA-C | Include Page |
PRQAPRQA0310Partially .Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this recommendation on the CERT website.
Related Guidelines
Secure representations Representations [STR] |
MISRA |
-Rule 3.5 Bibliography
[Plum 1985] | Rule 6-5: In portable code, do not depend upon the allocation order of bit-fields within a word |
...
...
Image Modified Image Modified Image Modified