1851
The product generates a query intended to access or manipulate data in a data store such as a
database, but it does not neutralize or incorrectly neutralizes special elements that can modify the
intended logic of the query.
Extended Description
Depending on the capabilities of the query language, an attacker could inject additional logic into
the query to:
• Modify the intended selection criteria, thus changing which data entities (e.g., records) are
returned, modified, or otherwise manipulated
• Append additional commands to the query
• Return more entities than intended
• Return fewer entities than intended
• Cause entities to be sorted in an unexpected way
The ability to execute additional commands or change which entities are returned has obvious
risks. But when the product logic depends on the order or number of entities, this can also lead
to vulnerabilities. For example, if the query expects to return only one entity that specifies an
administrative user, but an attacker can change which entities are returned, this could cause the
logic to return information for a regular user and incorrectly assume that the user has administrative
privileges.
While this weakness is most commonly associated with SQL injection, there are many other query
languages that are also subject to injection attacks, including HTSQL, LDAP, DQL, XQuery, Xpath,
and "NoSQL" languages.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 74 Improper Neutralization of Special Elements in Output Used
by a Downstream Component ('Injection')