This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Top 10-2017 A1-Injection"
From OWASP
(Created page with "{{Top_10_2013:TopTemplate |usenext=2013NextLink |next=A2-{{Top_10_2010:ByTheNumbers |2 |year=2017 |language=en}} |useprev...") |
m (underlined all links and Scenario #1/2, redefined links to OWASP as internal links) |
||
| Line 20: | Line 20: | ||
</td> | </td> | ||
| − | <td colspan=2 {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2017}}>[[Injection_Flaws | Injection flaws]] occur when an application sends untrusted data to an interpreter. Injection flaws are very prevalent, particularly in legacy code. They are often found in SQL, LDAP, XPath, or NoSQL queries; OS commands; XML parsers, SMTP Headers, expression languages, etc. Injection flaws are easy to discover when examining code, but frequently hard to discover via testing. Scanners and fuzzers can help attackers find injection flaws. | + | <td colspan=2 {{Template:Top 10 2010:SummaryTableRowStyleTemplate|year=2017}}><u>[[Injection_Flaws | Injection flaws]]</u> occur when an application sends untrusted data to an interpreter. Injection flaws are very prevalent, particularly in legacy code. They are often found in SQL, LDAP, XPath, or NoSQL queries; OS commands; XML parsers, SMTP Headers, expression languages, etc. Injection flaws are easy to discover when examining code, but frequently hard to discover via testing. Scanners and fuzzers can help attackers find injection flaws. |
</td> | </td> | ||
| Line 39: | Line 39: | ||
Preventing injection requires keeping untrusted data separate from commands and queries. | Preventing injection requires keeping untrusted data separate from commands and queries. | ||
# The preferred option is to use a safe API which avoids the use of the interpreter entirely or provides a parameterized interface. Be careful with APIs, such as stored procedures, that are parameterized, but can still introduce injection under the hood. | # The preferred option is to use a safe API which avoids the use of the interpreter entirely or provides a parameterized interface. Be careful with APIs, such as stored procedures, that are parameterized, but can still introduce injection under the hood. | ||
| − | # If a parameterized API is not available, you should carefully escape special characters using the specific escape syntax for that interpreter. [ | + | # If a parameterized API is not available, you should carefully escape special characters using the specific escape syntax for that interpreter. <u>[[OWASP_Java_Encoder_Project|OWASP’s Java Encoder]]</u> and similar libraries provide such escaping routines. |
| − | # Positive or “white list” input validation is also recommended, but is <u>not</u> a complete defense as many situations require special characters be allowed. If special characters are required, only approaches (1) and (2) above will make their use safe. [ | + | # Positive or “white list” input validation is also recommended, but is <u>not</u> a complete defense as many situations require special characters be allowed. If special characters are required, only approaches (1) and (2) above will make their use safe. <u>[[ESAPI|OWASP’s ESAPI]]</u> has an extensible library of <u>[https://static.javadoc.io/org.owasp.esapi/esapi/2.1.0.1/org/owasp/esapi/Validator.html white list input validation routines]</u>. |
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2017|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=example|position=left|risk=1|year=2017|language=en}} | ||
| − | '''Scenario #1:''' An application uses untrusted data in the construction of the following '''vulnerable''' SQL call: | + | <u>'''Scenario #1:'''</u> An application uses untrusted data in the construction of the following '''vulnerable''' SQL call: |
{{Top_10_2010:ExampleBeginTemplate|year=2017}}<span style="color:red;"> | {{Top_10_2010:ExampleBeginTemplate|year=2017}}<span style="color:red;"> | ||
| Line 49: | Line 49: | ||
</span>{{Top_10_2010:ExampleEndTemplate}} | </span>{{Top_10_2010:ExampleEndTemplate}} | ||
| − | '''Scenario #2:''' Similarly, an application’s blind trust in frameworks may result in queries that are still vulnerable, (e.g., Hibernate Query Language (HQL)): | + | |
| + | |||
| + | <u>'''Scenario #2:'''</u> Similarly, an application’s blind trust in frameworks may result in queries that are still vulnerable, (e.g., Hibernate Query Language (HQL)): | ||
{{Top_10_2010:ExampleBeginTemplate|year=2017}}<span style="color:red;"> | {{Top_10_2010:ExampleBeginTemplate|year=2017}}<span style="color:red;"> | ||
Query HQLQuery = session.createQuery("FROM accounts | Query HQLQuery = session.createQuery("FROM accounts | ||
| Line 64: | Line 66: | ||
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=references|position=right|risk=1|year=2017|language=en}} | {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=references|position=right|risk=1|year=2017|language=en}} | ||
{{Top_10_2010:SubSubsectionOWASPReferencesTemplate}} | {{Top_10_2010:SubSubsectionOWASPReferencesTemplate}} | ||
| − | * [[SQL_Injection_Prevention_Cheat_Sheet | OWASP SQL Injection Prevention Cheat Sheet]] | + | * <u>[[SQL_Injection_Prevention_Cheat_Sheet | OWASP SQL Injection Prevention Cheat Sheet]]</u> |
| − | * [[Query_Parameterization_Cheat_Sheet | OWASP Query Parameterization Cheat Sheet]] | + | * <u>[[Query_Parameterization_Cheat_Sheet | OWASP Query Parameterization Cheat Sheet]]</u> |
| − | * [[Command_Injection | OWASP Command Injection Article]] | + | * <u>[[Command_Injection | OWASP Command Injection Article]]</u> |
| − | * [[XML_External_Entity_(XXE)_Prevention_Cheat_Sheet| OWASP XXE Prevention Cheat Sheet]] | + | * <u>[[XML_External_Entity_(XXE)_Prevention_Cheat_Sheet| OWASP XXE Prevention Cheat Sheet]]</u> |
| − | * [[Testing_for_SQL_Injection_(OTG-INPVAL-005)|OWASP Testing Guide: Chapter on SQL Injection Testing]] | + | * <u>[[Testing_for_SQL_Injection_(OTG-INPVAL-005)|OWASP Testing Guide: Chapter on SQL Injection Testing]]</u> |
| + | |||
{{Top_10_2010:SubSubsectionExternalReferencesTemplate}} | {{Top_10_2010:SubSubsectionExternalReferencesTemplate}} | ||
| − | * [http://cwe.mitre.org/data/definitions/77.html CWE Entry 77 on Command Injection] | + | * <u>[http://cwe.mitre.org/data/definitions/77.html CWE Entry 77 on Command Injection]</u> |
| − | * [http://cwe.mitre.org/data/definitions/89.html CWE Entry 89 on SQL Injection] | + | * <u>[http://cwe.mitre.org/data/definitions/89.html CWE Entry 89 on SQL Injection]</u> |
| − | * [http://cwe.mitre.org/data/definitions/564.html CWE Entry 564 on Hibernate Injection] | + | * <u>[http://cwe.mitre.org/data/definitions/564.html CWE Entry 564 on Hibernate Injection]</u> |
| − | * [http://cwe.mitre.org/data/definitions/611.html CWE Entry 611 on Improper Restriction of XXE] | + | * <u>[http://cwe.mitre.org/data/definitions/611.html CWE Entry 611 on Improper Restriction of XXE]</u> |
| − | * [http://cwe.mitre.org/data/definitions/917.html|CWE Entry 917 on Expression Language Injection] | + | * <u>[http://cwe.mitre.org/data/definitions/917.html|CWE Entry 917 on Expression Language Injection]</u> |
{{Top_10_2013:BottomAdvancedTemplate | {{Top_10_2013:BottomAdvancedTemplate | ||
Revision as of 12:13, 23 April 2017
| Threat Agents / Attack Vectors | Security Weakness | Impacts | |||
|---|---|---|---|---|---|
| App Specific | Exploitability EASY |
Prevalence COMMON |
Detectability AVERAGE |
Impact SEVERE |
Business ? |
| Consider anyone who can send untrusted data to the system, including external users, internal users, and administrators. | Attackers send simple text-based attacks that exploit the syntax of the targeted interpreter. Almost any source of data can be an injection vector, including internal sources. | Injection flaws occur when an application sends untrusted data to an interpreter. Injection flaws are very prevalent, particularly in legacy code. They are often found in SQL, LDAP, XPath, or NoSQL queries; OS commands; XML parsers, SMTP Headers, expression languages, etc. Injection flaws are easy to discover when examining code, but frequently hard to discover via testing. Scanners and fuzzers can help attackers find injection flaws. | Injection can result in data loss or corruption, lack of accountability, or denial of access. Injection can sometimes lead to complete host takeover.
|
Consider the business value of the affected data and the platform running the interpreter. All data could be stolen, modified, or deleted. Could your reputation be harmed? | |
|
Am I Vulnerable To 'Injection'?
The best way to find out if an application is vulnerable to injection is to verify that all use of interpreters clearly separates untrusted data from the command or query. In many cases, it is recommended to avoid the interpreter, or disable it (e.g., XXE), if possible. For SQL calls, use bind variables in all prepared statements and stored procedures, or avoid dynamic queries. Checking the code is a fast and accurate way to see if the application uses interpreters safely. Code analysis tools can help a security analyst find use of interpreters and trace data flow through the application. Penetration testers can validate these issues by crafting exploits that confirm the vulnerability. Automated dynamic scanning which exercises the application may provide insight into whether some exploitable injection flaws exist. Scanners cannot always reach interpreters and have difficulty detecting whether an attack was successful. Poor error handling makes injection flaws easier to discover. |
How Do I Prevent 'Injection'?
Preventing injection requires keeping untrusted data separate from commands and queries.
|
|
Example Attack Scenarios
Scenario #1: An application uses untrusted data in the construction of the following vulnerable SQL call: String query = "SELECT * FROM accounts WHERE custID='" + request.getParameter("id") + "'";
Query HQLQuery = session.createQuery("FROM accounts WHERE custID='" + request.getParameter("id") + "'"); In both cases, the attacker modifies the ‘id’ parameter value in her browser to send: ' or '1'='1. For example:
http://example.com/app/accountView?id=' or '1'='1
This changes the meaning of both queries to return all the records from the accounts table. More dangerous attacks could modify data or even invoke stored procedures. |
References
OWASP
External |
