Reino: Input Validation and Representation

Problemas de validação e representação da entrada são causados por metacaracteres, codificações alternativas e representações numéricas. Confiar na entrada resulta em problemas de segurança. Os problemas incluem: “Buffer Overflows”, ataques de “Cross-Site Scripting”, “SQL Injection”, entre outros.

Expression Language Injection: Spring

Java/JSP

Abstract

A avaliação de expressões SpEL não validadas pode levar a uma execução remota de código.

Explanation

A Spring Expression Language (SpEL para abreviar) é uma linguagem de expressão poderosa que suporta a consulta e a manipulação de um gráfico de objetos em tempo de execução. A sintaxe de linguagem é semelhante ao EL Unificado, mas oferece recursos adicionais, principalmente a invocação do método e a funcionalidade básica do modelo de string.
Permitir que expressões não validadas sejam avaliadas permitirá que um invasor execute um código arbitrário.

Exemplo 1: O aplicativo usa dados não validados controlados pelo usuário para criar e avaliar uma expressão SpEL:


String expression = request.getParameter("input");
SpelExpressionParser parser = new SpelExpressionParser();
SpelExpression expr = parser.parseRaw(expression);

Exemplo 2: O aplicativo usa dados não validados controlados pelo usuário em uma tag Spring que realiza a avaliação dupla SpEL:


    <spring:message text="" code="${param['message']}"></spring:message>

References

[1] Dan Amodio Remote Code with Expression Language Injection

[2] Expression Language Injection OWASP

[3] CVE-2011-2730 Red Hat

[4] Standards Mapping - CIS Azure Kubernetes Service Benchmark 4

[5] Standards Mapping - CIS Microsoft Azure Foundations Benchmark complete

[6] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 4

[7] Standards Mapping - CIS Amazon Web Services Foundations Benchmark 4

[8] Standards Mapping - CIS Google Cloud Computing Platform Benchmark complete

[9] Standards Mapping - CIS Google Kubernetes Engine Benchmark integrity

[10] Standards Mapping - CIS Kubernetes Benchmark complete

[11] Standards Mapping - Common Weakness Enumeration CWE ID 94, CWE ID 95, CWE ID 917

[12] Standards Mapping - Common Weakness Enumeration Top 25 2019 [18] CWE ID 094

[13] Standards Mapping - Common Weakness Enumeration Top 25 2020 [17] CWE ID 094

[14] Standards Mapping - Common Weakness Enumeration Top 25 2021 [25] CWE ID 077

[15] Standards Mapping - Common Weakness Enumeration Top 25 2022 [17] CWE ID 077, [25] CWE ID 094

[16] Standards Mapping - Common Weakness Enumeration Top 25 2023 [16] CWE ID 077, [23] CWE ID 094

[17] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-002754

[18] Standards Mapping - FIPS200 SI

[19] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data

[20] Standards Mapping - NIST Special Publication 800-53 Revision 4 SI-10 Information Input Validation (P1)

[21] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-10 Information Input Validation

[22] Standards Mapping - OWASP Top 10 2004 A6 Injection Flaws

[23] Standards Mapping - OWASP Top 10 2007 A2 Injection Flaws

[24] Standards Mapping - OWASP Top 10 2010 A1 Injection

[25] Standards Mapping - OWASP Top 10 2013 A1 Injection

[26] Standards Mapping - OWASP Top 10 2017 A1 Injection

[27] Standards Mapping - OWASP Top 10 2021 A03 Injection

[28] Standards Mapping - OWASP Application Security Verification Standard 4.0 5.2.4 Sanitization and Sandboxing Requirements (L1 L2 L3), 5.2.5 Sanitization and Sandboxing Requirements (L1 L2 L3), 5.2.8 Sanitization and Sandboxing Requirements (L1 L2 L3), 5.3.6 Output Encoding and Injection Prevention Requirements (L1 L2 L3)

[29] Standards Mapping - OWASP Mobile 2014 M1 Weak Server Side Controls

[30] Standards Mapping - OWASP Mobile 2024 M4 Insufficient Input/Output Validation

[31] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.6

[32] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.3.1.1, Requirement 6.5.2

[33] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.1

[34] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.1

[35] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.1

[36] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.1

[37] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.1

[38] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4

[39] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 4.2 - Critical Asset Protection

[40] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 4.2 - Critical Asset Protection, Control Objective B.3.1 - Terminal Software Attack Mitigation, Control Objective B.3.1.1 - Terminal Software Attack Mitigation

[41] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 4.2 - Critical Asset Protection, Control Objective B.3.1 - Terminal Software Attack Mitigation, Control Objective B.3.1.1 - Terminal Software Attack Mitigation, Control Objective C.3.2 - Web Software Attack Mitigation

[42] Standards Mapping - SANS Top 25 2009 Risky Resource Management - CWE ID 094

[43] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3510 CAT I, APP3570 CAT I

[44] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3510 CAT I, APP3570 CAT I

[45] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3510 CAT I, APP3570 CAT I

[46] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3510 CAT I, APP3570 CAT I

[47] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3510 CAT I, APP3570 CAT I

[48] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3510 CAT I, APP3570 CAT I

[49] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3510 CAT I, APP3570 CAT I

[50] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002560 CAT I

[51] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002560 CAT I

[52] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002560 CAT I

[53] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002560 CAT I

[54] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002560 CAT I

[55] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002560 CAT I

[56] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002560 CAT I

[57] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002560 CAT I

[58] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002560 CAT I

[59] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002560 CAT I

[60] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002560 CAT I

[61] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002560 CAT I

[62] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002560 CAT I

[63] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002530 CAT II, APSC-DV-002560 CAT I

[64] Standards Mapping - Web Application Security Consortium Version 2.00 Improper Input Handling (WASC-20)

desc.dataflow.java.expression_language_injection_spring