CWE-89 (SQL命令中使用的特殊元素转义处理不恰当(SQL注入)) — Vulnerability Class 10996

10996 vulnerabilities classified as CWE-89 (SQL命令中使用的特殊元素转义处理不恰当(SQL注入)). AI Chinese analysis included.

CWE-89 represents a critical input validation weakness where software constructs SQL commands using untrusted data without properly sanitizing special characters. Attackers typically exploit this vulnerability by injecting malicious SQL syntax into user-facing inputs, such as login fields or search queries, to manipulate the database’s behavior. This exploitation can lead to unauthorized data access, data modification, or complete system compromise by bypassing authentication or executing arbitrary commands. Developers mitigate this risk by implementing strict input validation and, most effectively, using parameterized queries or prepared statements. These techniques ensure that user input is treated strictly as data rather than executable code, thereby preventing the injection of malicious SQL elements. By separating code logic from data inputs, applications maintain integrity and protect sensitive information from unauthorized manipulation.

MITRE CWE Description

The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Common Consequences (5)

Confidentiality, Integrity, Availability Execute Unauthorized Code or Commands

Adversaries could execute system commands, typically by changing the SQL statement to redirect output to a file that can then be executed.

Confidentiality Read Application Data

Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.

Authentication Gain Privileges or Assume Identity, Bypass Protection Mechanism

If poor SQL commands are used to check user names and passwords or perform other kinds of authentication, it may be possible to connect to the product as another user with no previous knowledge of the password.

Access Control Bypass Protection Mechanism

If authorization information is held in a SQL database, it may be possible to change this information through the successful exploitation of a SQL injection vulnerability.

Integrity Modify Application Data

Just as it may be possible to read sensitive information, it is also possible to modify or even delete this information with a SQL injection attack.

Mitigations (5)

Architecture and Design Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.

Architecture and Design If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated. Process SQL queries using prepared statements, parameterized queries, or stored procedur…

Architecture and Design, Operation Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database ad…

Architecture and Design For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

Implementation While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict allowlist (such as everything that is not alphanumeric or whit…

Examples (2)

In 2008, a large number of web servers were compromised using the same SQL injection attack string. This single string worked against many different programs. The SQL injection was then used to modify the web sites to serve malicious code.

The following code dynamically constructs and executes a SQL query that searches for items matching a specified name. The query restricts the items displayed to those where owner matches the user name of the currently-authenticated user.

... string userName = ctx.getAuthenticatedUserName(); string query = "SELECT * FROM items WHERE owner = '" + userName + "' AND itemname = '" + ItemName.Text + "'"; sda = new SqlDataAdapter(query, conn); DataTable dt = new DataTable(); sda.Fill(dt); ...

Bad · C#

SELECT * FROM items WHERE owner = <userName> AND itemname = <itemName>;

Informative

CVE ID	Title	CVSS	Severity	Published
CVE-2017-12364	Cisco Prime Service Catalog SQL注入漏洞 — Cisco Prime Service Catalog	6.5	-	2017-11-30
CVE-2017-12302	Cisco Unified Communications Manager SQL数据库界面SQL注入漏洞 — Cisco Unified Communications Manager	4.3	-	2017-11-16
CVE-2017-12731	多款OPW产品SQL注入漏洞 — OPW Fuel Management Systems SiteSentinel Integra and SiteSentinel iSite	9.8	-	2017-09-09
CVE-2017-11161	Synology Photo Station SQL注入漏洞 — Synology Photo Station	9.8	-	2017-09-08
CVE-2017-12227	Cisco Emergency Responder SQL注入漏洞 — Cisco Emergency Responder	5.4	-	2017-09-07
CVE-2017-12710	Advantech WebAccess SQL注入漏洞 — Advantech WebAccess	7.5	-	2017-08-30
CVE-2017-6754	Cisco Smart Net Total Care Software Collector Appliance SQL注入漏洞 — Cisco Smart Net Total Care Software Collector Appliance	6.5	-	2017-08-07
CVE-2017-6757	Cisco Unified Communications Manager SQL注入漏洞 — Cisco Unified Communications Manager	8.8	-	2017-08-07
CVE-2017-3221	AmosConnect 8 SQL注入漏洞 — AmosConnect	7.5	-	2017-07-22
CVE-2017-6050	Ecava IntegraXor SQL注入漏洞 — Ecava IntegraXor	9.8	-	2017-06-21
CVE-2014-2376	Ecava IntegraXor SCADA Server SQL Injection — IntegraXor SCADA Server	9.8	-	2014-09-15
CVE-2014-5399	Schneider Electric Wonderware SQL Injection — Wonderware Information Server Portal	9.8	-	2014-08-28
CVE-2014-2351	CSWorks SQL Injection — CSWorks	9.8	-	2014-05-20
CVE-2014-0763	Advantech WebAccess SQL Injection — WebAccess	9.8	-	2014-04-12
CVE-2012-6427	Carlo Gavazzi EOS Box SQL Injection — EOS-Box	9.8	-	2012-12-23
CVE-2012-5861	Sinapsi eSolar SQL Injection — eSolar	9.8	-	2012-11-23

Vulnerabilities classified as CWE-89 (SQL命令中使用的特殊元素转义处理不恰当(SQL注入)) represent 10996 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.