According to Section the C Standard, 7.4 of C99.1 paragraph 1 [ISO/IEC 9899:2024],
The header
<ctype.h>
declares several functions useful for classifying and mapping characters. In all cases the argument is anint
, the value of which shall be representable as anunsigned char
or shall equal the value of the macroEOF
. If the argument has any other value, the behavior is undefined.
See also undefined behavior 113.
Compliance with this This rule is complicated by the fact that applicable only to code that runs on platforms where the char
data type might, in any implementation, be signed or unsigned.is defined to have the same range, representation, and behavior as signed char
.
Following are the character classification functions that this rule addressesThe following character classification functions are affected:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
XSI denotes an X/Open System Interfaces Extension to ISO/IEC 9945—POSIX. These functions are not defined by the C Standard.
This rule is a specific instance of STR34-C. Cast characters to unsigned char before converting to larger integer sizes.
Noncompliant Code Example
This noncompliant code example may pass invalid values to the isspace()
function.On implementations where plain char
is signed, this code example is noncompliant because the parameter to isspace()
, *t
, is defined as a const char *
, and this value might not be representable as an unsigned char
:
Code Block | ||||
---|---|---|---|---|
| ||||
#include <ctype.h> #include <string.h> size_t count_preceding_whitespace(const char *s) { const char *t = s; size_t length = strlen(s) + 1; /* possibly *t < 0 */ while (isspace(*t) && (t - s < length)) { ++t; } return t - s; } |
The argument to isspace()
must be EOF
or representable as an unsigned char
; otherwise, the result is undefined.
Compliant Solution
...
This compliant solution casts the character to unsigned char
before passing it as an argument to the isspace()
function:Pass character strings around explicitly using unsigned characters.
Code Block | ||||
---|---|---|---|---|
| ||||
#include <ctype.h> #include <string.h> size_t count_preceding_whitespace(const char *s) { const unsigned char *t = s; size_t length = strlen(s) + 1; while (isspace((unsigned char)*t) && (t - s < length)) { ++t; } return t - s; } |
Wiki Markup |
---|
This approach is inconvenient when you need to interwork with other functions that haven't been designed with this approach in mind, such as the string handling functions found in the standard library \[[Kettlewell 02|AA. C References#Kettlewell 02]\]. |
Compliant Solution (Cast)
This compliant solution uses a cast.
Code Block | ||
---|---|---|
| ||
size_t count_preceding_whitespace(const char *s) {
const char *t = s;
size_t length = strlen(s) + 1;
while (isspace((unsigned char)*t) && (t - s < length)) {
++t;
}
return t - s;
}
|
Automated Detection
...
|
Risk Assessment
Passing values to character handling functions that cannot be represented as an unsigned char
to character handling functions is undefined behavior.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
STR37-C | Low | Unlikely | Low | P3 | L3 |
Automated Detection
Tool | Version | Checker | Description | ||||||
---|---|---|---|---|---|---|---|---|---|
Astrée |
| ctype-limits | Partially checked | ||||||
Axivion Bauhaus Suite |
| CertC-STR37 | Fully implemented | ||||||
CodeSonar |
| MISC.NEGCHAR | Negative character value | ||||||
Compass/ROSE | Could detect violations of this rule by seeing if the argument to a character |
...
handling function (listed above) is not an | ||||||||
| CC2. |
...
STR37 | Fully implemented | ||||||||
Helix QAC |
| C4413, C4414 C++3051 | |||||||
Klocwork |
| AUTOSAR.STDLIB.CCTYPE.UCHAR MISRA.ETYPE.ASSIGN.2012 | |||||||
LDRA tool suite |
| 663 S | Fully implemented | ||||||
Parasoft C/C++test |
| CERT_C-STR37-a | Do not pass incorrect values to ctype.h library functions | ||||||
Polyspace Bug Finder |
| Checks for invalid use of standard library integer routine (rule fully covered) | |||||||
RuleChecker |
| ctype-limits | Partially checked | ||||||
TrustInSoft Analyzer |
| valid_char | Partially verified. |
Risk Assessment
Passing values to character handling functions that cannot be represented as an unsigned char
may result in unintended program behavior.
Rule
Severity
Likelihood
Remediation Cost
Priority
Level
STR37-C
low
unlikely
low
P3
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
References
Wiki Markup |
---|
\[[ISO/IEC 9899:1999|AA. C References#ISO/IEC 9899-1999]\] Section 7.4, "Character handling <{{ctype.h}}>"
\[[Kettlewell 02|AA. C References#Kettle 02]\] Section 1.1, "<{{ctype.h}}> And Characters Types" |
Related Guidelines
Key here (explains table format and definitions)
Taxonomy | Taxonomy item | Relationship |
---|---|---|
CERT C Secure Coding Standard | STR34-C. Cast characters to unsigned char before converting to larger integer sizes | Prior to 2018-01-12: CERT: Unspecified Relationship |
ISO/IEC TS 17961 | Passing arguments to character-handling functions that are not representable as unsigned char [chrsgnext] | Prior to 2018-01-12: CERT: Unspecified Relationship |
CWE 2.11 | CWE-704, Incorrect Type Conversion or Cast | 2017-06-14: CERT: Rule subset of CWE |
CERT-CWE Mapping Notes
Key here for mapping notes
CWE-686 and STR37-C
Intersection( CWE-686, STR37-C) = Ø
STR37-C is not about the type of the argument passed (which is signed int), but about the restrictions placed on the value in this type (must be 0-UCHAR_MAX or EOF). I interpret ‘argument type’ to be specific to the C language, so CWE-686 does not apply to incorrect argument values, just incorrect types (which is relatively rare in C, but still possible).
CWE-704 and STR37-C
STR37-C = Subset( STR34-C)
CWE-683 and STR37-C
Intersection( CWE-683, STR37-C) = Ø
STR37-C excludes mis-ordered function arguments (assuming they pass type-checking), because there is no easy way to reliably detect violations of CWE-683.
Bibliography
[ISO/IEC 9899:2024] | 7.4.1, "Character Handling <ctype.h >" |
[Kettlewell 2002] | Section 1.1, "<ctype.h > and Characters Types" |
...
STR36-C. Do not specify the bound of a character array initialized with a string literal 07. Characters and Strings (STR) 08. Memory Management (MEM)