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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

10255 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-2023-20271 Cisco Evolved Programmable Network Manager 安全漏洞 — Cisco Prime Infrastructure 6.5 Medium 2024-01-17
CVE-2024-0405 Burst Statistics Really Simple Plugins <= 1.5.3 - Authenticated (Editor+) SQL Injection — Burst Statistics – Privacy-Friendly WordPress Analytics (Google Analytics Alternative) 7.2 High 2024-01-17
CVE-2024-22406 Blind SQL-injection in DAL aggregations in Shopware — shopware 9.3 Critical 2024-01-16
CVE-2024-0558 DedeBIZ makehtml_freelist_action.php sql injection — DedeBIZ 4.7 Medium 2024-01-15
CVE-2024-0543 CodeAstro Real Estate Management System propertydetail.php sql injection — Real Estate Management System 6.3 Medium 2024-01-15
CVE-2024-0530 CXBSoft Post-Office HTTP POST Request reg_go.php sql injection — Post-Office 5.5 Medium 2024-01-15
CVE-2024-0529 CXBSoft Post-Office HTTP POST Request login_auth.php sql injection — Post-Office 5.5 Medium 2024-01-15
CVE-2024-0528 CXBSoft Post-Office HTTP POST Request update_go.php sql injection — Post-Office 5.5 Medium 2024-01-15
CVE-2024-0527 CXBSoft Url-shorting HTTP POST Request update_go.php sql injection — Url-shorting 6.3 Medium 2024-01-15
CVE-2024-0526 CXBSoft Url-shorting HTTP POST Request short_to_long.php sql injection — Url-shorting 5.5 Medium 2024-01-15
CVE-2024-0525 CXBSoft Url-shorting HTTP POST Request long_s_short.php sql injection — Url-shorting 5.5 Medium 2024-01-14
CVE-2024-0524 CXBSoft Url-shorting index.php sql injection — Url-shorting 5.5 Medium 2024-01-14
CVE-2024-0523 CmsEasy language_admin.php getslide_child_action sql injection — CmsEasy 6.3 Medium 2024-01-14
CVE-2024-0502 SourceCodester House Rental Management System Edit User manage_user.php sql injection — House Rental Management System 4.7 Medium 2024-01-13
CVE-2024-0498 Project Worlds Lawyer Management System searchLawyer.php sql injection — Lawyer Management System 6.3 Medium 2024-01-13
CVE-2024-0497 Campcodes Student Information System sql injection — Student Information System 6.3 Medium 2024-01-13
CVE-2024-0496 Kashipara Billing Software HTTP POST Request item_list_edit.php sql injection — Billing Software 6.3 Medium 2024-01-13
CVE-2024-0495 Kashipara Billing Software HTTP POST Request party_submit.php sql injection — Billing Software 6.3 Medium 2024-01-13
CVE-2024-0494 Kashipara Billing Software HTTP POST Request material_bill.php sql injection — Billing Software 6.3 Medium 2024-01-13
CVE-2024-0493 Kashipara Billing Software HTTP POST Request submit_delivery_list.php sql injection — Billing Software 6.3 Medium 2024-01-13
CVE-2024-0492 Kashipara Billing Software HTTP POST Request buyer_detail_submit.php sql injection — Billing Software 6.3 Medium 2024-01-13
CVE-2024-0489 code-projects Fighting Cock Information System edit_chicken.php sql injection — Fighting Cock Information System 6.3 Medium 2024-01-13
CVE-2024-0488 code-projects Fighting Cock Information System new-feed.php sql injection — Fighting Cock Information System 6.3 Medium 2024-01-13
CVE-2024-0487 code-projects Fighting Cock Information System delete-vaccine.php sql injection — Fighting Cock Information System 6.3 Medium 2024-01-13
CVE-2024-0486 code-projects Fighting Cock Information System add_con.php sql injection — Fighting Cock Information System 6.3 Medium 2024-01-13
CVE-2024-0485 code-projects Fighting Cock Information System add_con.php sql injection — Fighting Cock Information System 6.3 Medium 2024-01-13
CVE-2024-0484 code-projects Fighting Cock Information System update_mother.php sql injection — Fighting Cock Information System 6.3 Medium 2024-01-13
CVE-2024-0483 Taokeyun HTTP POST Request Task.php index sql injection — Taokeyun 6.3 Medium 2024-01-13
CVE-2024-0482 Taokeyun HTTP POST Request Video.php index sql injection — Taokeyun 6.3 Medium 2024-01-13
CVE-2024-0481 Taokeyun HTTP POST Request Goods.php shopGoods sql injection — Taokeyun 6.3 Medium 2024-01-13

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