目标达成 感谢每一位支持者 — 我们达成了 100% 目标！

目标: 1000 元 · 已筹: 1310 元

100%
请我们喝杯咖啡

CWE-89 SQL命令中使用的特殊元素转义处理不恰当(SQL注入) 类漏洞列表 9217

CWE-89 SQL命令中使用的特殊元素转义处理不恰当(SQL注入) 类弱点 9217 条 CVE 漏洞汇总，含 AI 中文分析。

CWE-89即SQL注入，属于输入验证类漏洞。当软件未对用户输入进行充分净化或转义，直接将其拼接到SQL命令中时，攻击者可注入恶意SQL代码，从而篡改查询逻辑、绕过身份验证或窃取敏感数据。开发者应避免直接拼接字符串，转而使用参数化查询或预编译语句，确保用户输入仅被视为数据而非可执行代码，从而从根本上阻断注入路径。

MITRE CWE 官方描述
CWE：CWE-89 SQL 命令中特殊元素的不当中和（SQL 注入） 英文：产品使用来自上游组件的外部影响输入来构建 SQL 命令的全部或部分，但未对可能在将命令发送给下游组件时修改预期 SQL 命令的特殊元素进行中和或进行了不正确的中和。如果未在用户可控制的输入中充分移除或引用 SQL 语法，生成的 SQL 查询可能导致这些输入被解释为 SQL 而非普通用户数据。
常见影响 (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.
缓解措施 (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…
代码示例 (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标题CVSS风险等级Published
CVE-2017-6050 Ecava IntegraXor SQL注入漏洞 — Ecava IntegraXor 9.8 -2017-06-21
CVE-2014-2376 Ecava IntegraXor SCADA Server Stable SQL注入漏洞 — IntegraXor SCADA Server 9.8 -2014-09-15
CVE-2014-5399 Schneider Electric WIS Portal SQL注入漏洞 — Wonderware Information Server Portal 9.8 -2014-08-28
CVE-2014-2351 CSWorks SQL注入漏洞 — CSWorks 9.8 -2014-05-20
CVE-2014-0763 Advantech WebAccess SQL注入漏洞 — WebAccess 9.8 -2014-04-12
CVE-2012-6427 Carlo Gavazzi EOS-BOX SQL注入漏洞 — EOS-Box 9.8 -2012-12-23
CVE-2012-5861 Sinapsi eSolar产品信息泄露漏洞 — eSolar 9.8 -2012-11-23

CWE-89（SQL命令中使用的特殊元素转义处理不恰当(SQL注入)） 是常见的弱点类别，本平台收录该类弱点关联的 9217 条 CVE 漏洞。