GitHub
CERT Secure Coding

STR04-C. Use plain char for characters in the basic character set

There are three character types : char , signed char , and unsigned char . Compilers have the latitude to define char to have the same range, representation, and behavior as either signed char or unsigned char . Irrespective of the choice made, char is a separate type from the other two and is not compatible with either.

For characters in the basic character set, it does not matter which data type is used, except for type compatibility. Consequently, it is best to use plain char for character data for compatibility with standard string-handling functions.

In most cases, the only portable operators on plain char types are assignment and equality operators ( = , == , != ). An exception is the translation to and from digits. For example, if the char c is a digit, c - '0' is a value between 0 and 9.

Noncompliant Code Example

This noncompliant code example simply shows the standard string-handling function strlen() being called with a plain character string, a signed character string, and an unsigned character string. The strlen() function takes a single argument of type const char *:

Non-compliant code
size_t len;
char cstr[] = "char string";
signed char scstr[] = "signed char string";
unsigned char ucstr[] = "unsigned char string";

len = strlen(cstr);
len = strlen(scstr);  /* Warns when char is unsigned */
len = strlen(ucstr);  /* Warns when char is signed */

Compiling at high warning levels in compliance with MSC00-C. Compile cleanly at high warning levels causes warnings to be issued when

  • Converting from unsigned char[] to const char * when char is signed
  • Converting from signed char[] to const char * when char is defined to be unsigned

Casts are required to eliminate these warnings, but excessive casts can make code difficult to read and hide legitimate warning messages.

If this C code were compiled using a C++ compiler, conversions from unsigned char[] to const char * and from signed char[] to const char * would be flagged as errors requiring casts.

Compliant Solution

The compliant solution uses plain char for character data:

Compliant code
size_t len;
char cstr[] = "char string";

len = strlen(cstr);

Conversions are not required, and the code compiles cleanly at high warning levels without casts.

Risk Assessment

Failing to use plain char for characters in the basic character set can lead to excessive casts and less effective compiler diagnostics.

Recommendation Severity Likelihood Detectable Repairable Priority Level
STR04-C Low Unlikely No Yes P2 L3

Automated Detection

Tool

Version

Checker

Description

Astrée
25.10

Supported indirectly via MISRA C:2004 rule 6.1.
Axivion Bauhaus Suite

7.2.0

CertC-STR04
CodeSonar
9.1p0
LANG.TYPE.IAT
LANG.TYPE.ICA
LANG.TYPE.IOT
LANG.TYPE.MOT
Inappropriate assignment type
Inappropriate character arithmetic
Inappropriate operand type
Mismatched operand types
Compass/ROSE




ECLAIR
1.2

CC2.STR04

Fully implemented

EDG




Helix QAC

2025.2

C0432, C0674, C0699
LDRA tool suite
9.7.1
93 S, 101 S, 329 S, 432 S, 458 SPartially implemented
Parasoft C/C++test
2025.2
CERT_C-STR04-a

The plain char type shall be used only for the storage and use of character values

RuleChecker
25.10

Supported indirectly via MISRA C:2004 rule 6.1.
SonarQube C/C++ Plugin
3.11
S810

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

SEI CERT C++ Coding StandardVOID STR04-CPP. Use plain char for characters in the basic character set
MISRA C:2012

Rule 10.1 (required)
Rule 10.2 (required)
Rule 10.3 (required)
Rule 10.4 (required)