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.SQL : SQL Injection

Summary

Potentially-tainted data is used to construct an SQL query.

Properties

Class Name SQL Injection
Significance security
Mnemonic IO.INJ.SQL
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:89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CERT-C CERT-C:STR02-C Sanitize data passed to complex subsystems
DISA-6r1 DISA-6r1:V-222606 The application must validate all input.
  DISA-6r1:V-222607 The application must not be vulnerable to SQL Injection.
  DISA-6r1:V-222609 The application must not be subject to input handling vulnerabilities.
DISA-5r3 DISA-5r3:V-70265 The application must validate all input.
  DISA-5r3:V-70267 The application must not be vulnerable to SQL Injection.
  DISA-5r3:V-70271 The application must not be subject to input handling vulnerabilities.
DISA-4r3 DISA-4r3:V-70265 The application must validate all input.
  DISA-4r3:V-70267 The application must not be vulnerable to SQL Injection.
  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-16807 The designer will ensure the application is not vulnerable to SQL Injection, uses prepared or parameterized statements, does not use concatenation or replacement to build SQL queries, and does not directly access the tables in a database.
OWASP-2017 OWASP-2017:A1 Injection
OWASP-2021 OWASP-2021:A3 Injection
OWASP-2025 OWASP-2025:A05 Injection
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="SQL Injection"

Example

#include <stdio.h>
#include <sql.h>

RETCODE lookup_by_email (SQLHSTMT hstmt){
    int querylen; 
    SQLCHAR query[256];
    char useremail[128];

    printf("Enter your email address.");
    if (!fgets(useremail, 64, stdin)) return SQL_ERROR;    

    querylen = sprintf((char*)query, 
                       "SELECT * FROM userinfo WHERE email = %s", 
                       useremail);
    return SQLExecDirect(hstmt, query, querylen); /* 'SQL Injection' warning issued here */
}

Triggers

CodeSonar ships with library models that allow it to recognize functions such as libpq PQexec() and Win32 SQLPrepareA() that use one or more of their parameters to construct an SQL query. If one of these functions is called with a tainted value in one of those parameter positions, 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 SQL 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/.