Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

8957 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, AvailabilityExecute 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.
ConfidentialityRead Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
AuthenticationGain 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 ControlBypass 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.
IntegrityModify 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 DesignUse 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 DesignIf 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, OperationRun 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 DesignFor 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.
ImplementationWhile 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 IDTitleCVSSSeverityPublished
CVE-2019-7003 ACM SQL Injection — Avaya Control Manager 9.1 -2019-07-11
CVE-2019-11821 Synology Photo Station SQL注入漏洞 — Photo Station 7.3 High2019-06-30
CVE-2018-5404 The Quest Kace K1000 Appliance is vulnerable to multiple Blind SQL Injections. — K1000 Appliance 6.5 -2019-06-03
CVE-2019-1824 Cisco Prime Infrastructure and Evolved Programmable Network Manager SQL Injection Vulnerabilities — Cisco Prime Infrastructure 8.1 -2019-05-16
CVE-2019-1825 Cisco Prime Infrastructure and Evolved Programmable Network Manager SQL Injection Vulnerabilities — Cisco Prime Infrastructure 8.1 -2019-05-16
CVE-2019-10916 多款Siemens产品SQL注入漏洞 — SIMATIC PCS 7 V8.0 and earlier 8.8 -2019-05-14
CVE-2019-3797 Additional information exposure with Spring Data JPA derived queries — Spring Boot 5.3 -2019-05-06
CVE-2019-7001 Avaya IPOCC WebUI SQL Injection — IP Office Contact Center 8.1 -2019-04-04
CVE-2019-3792 Concourse 5.0.0 SQL Injection vulnerability — Concourse 7.5 -2019-04-01
CVE-2018-14623 Katello SQL注入漏洞 — katello 4.3 -2018-12-13
CVE-2018-15441 Cisco Prime License Manager SQL Injection Vulnerability — Cisco Prime License Manager 9.8 -2018-11-28
CVE-2018-18982 NUUO CMS SQL注入漏洞 — NUUO CMS 9.8 -2018-11-27
CVE-2018-16850 PostgreSQL SQL注入漏洞 — postgresql 9.8 -2018-11-13
CVE-2018-15447 Cisco Integrated Management Controller Supervisor SQL Injection Vulnerability — Cisco Integrated Management Controller (IMC) Supervisor 9.8 -2018-11-08
CVE-2018-0404 Cisco RV180W Wireless-N Multifunction VPN Router SQL Injection Vulnerability — Cisco RV180W Wireless-N Multifunction VPN Router 9.1 -2018-10-05
CVE-2018-12470 SQL injection in RegistrationSharing module — SMT 9.8 -2018-10-04
CVE-2016-8640 pycsw SQL注入漏洞 — pycsw 7.4 -2018-08-01
CVE-2017-3181 Multiple TIBCO Spotfire components are vulnerable to multiple unspecified SQL-injection vulnerabilities because it fails to properly sanitize user-supplied input before using it in an SQL query — Spotfire Analyst 9.8 -2018-07-24
CVE-2018-5384 Navarino Infinity web interface up to version 2.2 exposes an unauthenticated script that is prone to blind sql injection — Infinity 9.8 -2018-07-24
CVE-2016-6566 The Sungard eTRAKiT3 software version 3.2.1.17 may be vulnerable to SQL injection which may allow a remote unauthenticated attacker to run a subset of SQL commands against the back-end database — eTRAKiT3 9.8 -2018-07-13
CVE-2018-12464 Unauthenticated SQL injection in Micro Focus Secure Messaging Gateway — Secure Messaging Gateway 9.8 -2018-06-29
CVE-2018-1132 OpenDaylight SDNInterfaceapp SQL注入漏洞 — opendaylight 9.8 -2018-06-20
CVE-2011-0467 SQL injection in SUSE studio via select parameter — SUSE Studio Onsite 8.8 -2018-06-07
CVE-2018-0320 Cisco Prime Collaboration Provisioning SQL注入漏洞 — Cisco Prime Collaboration Provisioning unknown 9.8 -2018-06-07
CVE-2016-9488 ManageEngine Applications Manager versions 12 and 13 suffer from remote SQL injection vulnerabilities — Applications Manager 9.8 -2018-06-05
CVE-2016-10550 sequalize SQL注入漏洞 — sequelize node module 9.8 -2018-05-31
CVE-2016-10553 sequalize SQL注入漏洞 — sequelize node module 9.8 -2018-05-31
CVE-2016-10554 sequelize 安全漏洞 — sequelize node module 9.8 -2018-05-31
CVE-2015-9244 mysql node模块SQL注入漏洞 — mysql node module 9.8 -2018-05-29
CVE-2016-10551 waterline-sequel 安全漏洞 — waterline-sequel node module 9.8 -2018-05-29

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