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


IO.INJ.LIB : Library Injection

Summary

A library operation identifies a library by name, but the name string may have been tainted.

Properties

Class Name Library Injection
Significance security
Mnemonic IO.INJ.LIB
Categories
MisraC2025 MisraC2025:D.4.14 The validity of values received from external sources shall be checked
MisraC2023 MisraC2023:D.4.14 The validity of values received from external sources shall be checked
Misra2012 Misra2012:D.4.14 The validity of values received from external sources shall be checked
AUTOSARC++14 AUTOSARC++14:A27-0-1 Inputs from independent components shall be validated.
MisraC++2023 MisraC++2023:0.3.2 A function call shall not violate the function's preconditions
CWE CWE:114 Process Control
CERT-C CERT-C:STR02-C Sanitize data passed to complex subsystems
DISA-6r1 DISA-6r1:V-222604 The application must protect from command injection.
  DISA-6r1:V-222606 The application must validate all input.
  DISA-6r1:V-222609 The application must not be subject to input handling vulnerabilities.
DISA-5r3 DISA-5r3:V-70261 The application must protect from command injection.
  DISA-5r3:V-70265 The application must validate all input.
  DISA-5r3:V-70271 The application must not be subject to input handling vulnerabilities.
DISA-4r3 DISA-4r3:V-70261 The application must protect from command injection.
  DISA-4r3:V-70265 The application must validate all input.
  DISA-4r3:V-70271 The application must not be subject to input handling vulnerabilities.
DISA-3r10 DISA-3r10:V-6164 The designer will ensure the application validates all input.
  DISA-3r10:V-16810 The designer will ensure the application does not allow command injection.
OWASP-2017 OWASP-2017:A1 Injection
OWASP-2021 OWASP-2021:A3 Injection
  OWASP-2021:A4 Insecure design
OWASP-2025 OWASP-2025:A05 Injection
  OWASP-2025:A06 Insecure Design
Availability Available for C and C++.
Enabling Checks for this warning class are enabled by default. To disable them, add the following WARNING_FILTER rule to the project configuration file.
WARNING_FILTER += discard class="Library Injection"

Example

#include <stdio.h>
#include <string.h>
#include <unistd.h>
int uselib(const char *library);
int load_mylib(void){
    int ret;
    char libpath[256];
    ret = uselib("/lib/mylib.so.2");
    if (!ret) return 0;

    ret = uselib("/usr/lib/mylib.so.2");
    if (!ret) return 0;

    printf("Could not find mylib: please enter location");
    if (!fgets(libpath, 128, stdin)) return -1;
    return uselib(strcat(libpath, "mylib.so.2"));  /* 'Library Injection' warning issued here */
}

Triggers

CodeSonar ships with library models that allow it to recognize functions such as libc dlopen() and Win32 LoadLibraryA() that take a library name parameter. If one of these functions is called with a tainted value in the library name parameter position, a warning will be issued.

If you have created a custom library model for some function f() in terms of one of these existing models, calls to f() will also be capable of triggering Library Injection warnings.

Relevant Configuration File Parameters

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

 

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