Unsanitized input in SQL query

Overview

• Rule ID: javascript_lang_sql_injection

• Applicable Languages: Javascript

• Weakness ID: CWE-89

Description

Using unsanitized data, such as user input, request data, or externally influenced data, in SQL queries exposes your application to SQL injection attacks. This vulnerability occurs when externally controlled data is directly included in SQL statements without proper sanitization, allowing attackers to manipulate queries and access or alter data.

Remediation Guidelines

• Avoid using raw SQL queries that directly concatenate unsanitized input.

  var sqlite = new Sequelize("sqlite::memory:");
  sqlite.query("SELECT * FROM users WHERE ID = " + req.params.userId); // unsafe
  

• Validate all query inputs to ensure they conform to expected patterns or values before using them in a query.

  var rawId = req.params.userId
  if !(/[0-9]+/.test(rawId)) {
    // input is unexpected; don't make the query
  }
  

• Use prepared (or parameterized) statements for database queries to safely incorporate external input.

  var sqlite = new Sequelize("sqlite::memory:");
  sqlite.query(
    "SELECT * FROM users WHERE ID = ?",
     { replacements: [req.params.userId] },
     type: sequelize.QueryTypes.SELECT
  )

References

• OWASP SQL injection explained

• OWASP SQL injection prevention cheat sheet

• CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

• OWASP Top 10: A03:2021 - Injection

Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our SAST TOOL