You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 147 Next »

Immutable objects should be const-qualified. Enforcing object immutability using const qualification helps ensure the correctness and security of applications. ISO/IEC TR 24772, for example, recommends labeling parameters as constant to avoid the unintentional modification of function arguments [ISO/IEC TR 24772]. STR05-C. Use pointers to const when referring to string literals describes a specialized case of this recommendation.

Adding const qualification may propagate through a program; as you add const, qualifiers become still more necessary. This phenomenon is sometimes called const poisoning, which can frequently lead to violations of EXP05-C. Do not cast away a const qualification. Although const qualification is a good idea, the costs may outweigh the value in the remediation of existing code.

A macro or an enumeration constant may also be used instead of a const-qualified object. DCL06-C. Use meaningful symbolic constants to represent literal values describes the relative merits of using const-qualified objects, enumeration constants, and object-like macros. However, adding a const qualifier to an existing variable is a better first step than replacing the variable with an enumeration constant or macro because the compiler will issue warnings on any code that changes your const-qualified variable. Once you have verified that a const-qualified variable is not changed by any code, you may consider changing it to an enumeration constant or macro, as best fits your design.

Noncompliant Code Example

In this noncompliant code, pi is declared as a float. Although pi is a mathematical constant, its value is not protected from accidental modification.

float pi = 3.14159f;
float degrees;
float radians;
/* ... */
radians = degrees * pi / 180;

Compliant Solution

In this compliant solution, pi is declared as a const-qualified object:

const float pi = 3.14159f;
float degrees;
float radians;
/* ... */
radians = degrees * pi / 180;

Risk Assessment

Failing to const-qualify immutable objects can result in a constant being modified at runtime.

Recommendation

Severity

Likelihood

Remediation Cost

Priority

Level

DCL00-C

Low

Unlikely

High

P1

L3

Automated Detection

Tool

Version

Checker

Description

Astrée
24.04
parameter-missing-constPartially checked
Axivion Bauhaus Suite

7.2.0

CertC-DCL00
CodeSonar
8.1p0

LANG.CAST.PC.CRCQ

LANG.TYPE.VCBC

Cast removes const qualifier

Variable Could Be const

Compass/ROSE




ECLAIR

1.2

CC2.DCL00

Partially implemented

Helix QAC

2024.3

C3204, C3227, C3232, C3673, C3677


LDRA tool suite
9.7.1

78 D
93 D
200 S

Fully implemented

Parasoft C/C++test
2023.1

CERT_C-DCL00-a

Declare parameters or local variable as const whenever possible

PC-lint Plus

1.4

953

Fully supported

PRQA QA-C
Unable to render {include} The included page could not be found.

3204, 3227,

3232, 3673,

3677

Partially implemented
RuleChecker
24.04
parameter-missing-constPartially checked

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

Related Guidelines

 Bibliography

[Dewhurst 2002]Gotcha #25, "#define Literals"
[Saks 2000]



  • No labels