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.

LDAP Entry Poisoning

Java/JSP

Abstract

Um aplicativo que executa uma pesquisa LDAP de retorno de objeto permitirá que invasores controlem a resposta LDAP para executar código arbitrário no servidor.

Explanation

Um invasor capaz de adulterar uma resposta LDAP, seja modificando a entrada em repouso ou interceptando e modificando a resposta em tempo real (ataque man-in-the-middle), será capaz de injetar atributos Java especiais na entrada LDAP. Ao realizar uma pesquisa de retorno de objeto, os atributos Java são decodificados como objetos Java usando a desserialização Java ou cancelamento de referência JNDI, permitindo que os invasores obtenham a execução remota de código no servidor de aplicativos que está executando a pesquisa.

O aplicativo executa uma pesquisa de retorno de objeto, definindo o returningObjectFlag como true na instãncia javax.naming.directory.SearchControls passada para o método search ou usando uma função de biblioteca que define este sinalizador em seu nome.

Nesse caso, o aplicativo está usando o módulo de autorização Spring Security LDAP que executa pesquisas de retorno de objeto e, portanto, é vulnerável ao envenenamento da entrada do LDAP.

Exemplo 1: O arquivo de configuração Beans a seguir configura o aplicativo para usar o módulo LDAP Spring Security como o provedor de autenticação.


<beans ... >
	<authentication-manager>
        <ldap-authentication-provider
            user-search-filter="(uid={0})"
            user-search-base="ou=users,dc=example,dc=org"
            group-search-filter="(uniqueMember={0})"
            group-search-base="ou=groups,dc=example,dc=org"
            group-role-attribute="cn"
            role-prefix="ROLE_">
        </ldap-authentication-provider>
	</authentication-manager>
</beans>

References

[1] Introducing JNDI Injection and LDAP Entry Poisoning OpenText Fortify

[2] A Journey from JNDI/LDAP manipulation to remote code execution dream land BlackHat

[3] Standards Mapping - Common Weakness Enumeration CWE ID 20

[4] Standards Mapping - Common Weakness Enumeration Top 25 2019 [3] CWE ID 020

[5] Standards Mapping - Common Weakness Enumeration Top 25 2020 [3] CWE ID 020

[6] Standards Mapping - Common Weakness Enumeration Top 25 2021 [4] CWE ID 020

[7] Standards Mapping - Common Weakness Enumeration Top 25 2022 [4] CWE ID 020

[8] Standards Mapping - Common Weakness Enumeration Top 25 2023 [6] CWE ID 020

[9] Standards Mapping - Common Weakness Enumeration Top 25 2024 [12] CWE ID 020

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

[11] Standards Mapping - FIPS200 SI

[12] Standards Mapping - General Data Protection Regulation (GDPR) Access Violation

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

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

[15] Standards Mapping - OWASP Application Security Verification Standard 4.0 5.1.3 Input Validation Requirements (L1 L2 L3), 5.1.4 Input Validation Requirements (L1 L2 L3)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[32] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 6.2.4

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

[34] 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

[35] 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

[36] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3510 CAT I

[37] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3510 CAT I

[38] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3510 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3510 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3510 CAT I

[41] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3510 CAT I

[42] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3510 CAT I

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

desc.configuration.java.ldap_entry_poisoning