JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

CodeSonar® 9.2p0 CONFIDENTIAL CodeSecure Inc
C and C++
Binaries

BADFUNC.BO.STRLEN : Use of strlen

Summary

A use of strlen() or a similar function (see full list below), which can lead to off-by-one errors and buffer overflows.

Properties

Class Name Use of strlen
Significance security
Mnemonic BADFUNC.BO.STRLEN
Categories
MisraC2025 MisraC2025:21.17 Use of the string handling functions from <string.h> shall not result in accesses beyond the bounds of the objects referenced by their pointer parameters
MisraC2023 MisraC2023:21.17 Use of the string handling functions from <string.h> shall not result in accesses beyond the bounds of the objects referenced by their pointer parameters
Misra2012 Misra2012:21.17 Use of the string handling functions from <string.h> shall not result in accesses beyond the bounds of the objects referenced by their pointer parameters
AUTOSARC++14 AUTOSARC++14:A5-2-5 An array or container shall not be accessed beyond its range.
  AUTOSARC++14:M18-0-5 The unbounded functions of library <cstring> shall not be used.
MisraC++2008 MisraC++2008:18-0-5 The unbounded functions of library <cstring> shall not be used.
MisraC++2023 MisraC++2023:21.2.2 The string handling functions from <cstring>, <cstdlib>, <cwchar> and <cinttypes> shall not be used
CWE CWE:120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
  CWE:676 Use of Potentially Dangerous Function
CERT-C CERT-C:API02-C Functions that read or write to or from an array should take an argument to specify the source or target size
  CERT-C:STR07-C Use the bounds-checking interfaces for string manipulation
CERT-CPP CERT-CPP:CTR52-CPP Guarantee that library functions do not overflow
DISA-6r1 DISA-6r1:V-222612 The application must not be vulnerable to overflow attacks.
DISA-5r3 DISA-5r3:V-70277 The application must not be vulnerable to overflow attacks.
DISA-4r3 DISA-4r3:V-70277 The application must not be vulnerable to overflow attacks.
DISA-3r10 DISA-3r10:V-6165 The designer will ensure the application does not have buffer overflows, use functions known to be vulnerable to buffer overflows, and does not use signed values for memory allocation where permitted by the programming language.
BSI BSI:STRLEN Use of strlen
OWASP-2021 OWASP-2021:A4 Insecure design
OWASP-2025 OWASP-2025:A06 Insecure Design
Availability Available for C and C++.
Enabling Checks for this warning class are disabled by default. To enable them, add the following WARNING_FILTER rule to the project configuration file. 
WARNING_FILTER += allow class="Use of strlen"
To enable all BSI-related classes, including all BSI-specific BADFUNC classes, use the bsi configuration preset.

Triggering Functions

Resolution

When you see a Use of strlen warning, make sure that user-supplied strings are explicitly null-terminated and statically-allocated string buffers have a null character in their final position before the string-length function is called. If so, you can change the warning state to Suppressed.

Alternatively, use strlen_s() or StringCchLength() instead of these functions.

Relevant Configuration File Parameters

This class is implemented using a BAD_FUNCTION_* rule set in the general template configuration file.

The following configuration file parameters affect checks for this warning class.

 

To report problems with this documentation, please visit https://support.codesecure.com/.