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.

Content Provider URI Injection

Java/JSP

Abstract

Construir uma instrução de Provedor de Conteúdo que contém entradas do usuário pode permitir que um invasor acesse registros não autorizados.

Explanation

Vulnerabilidades de injeção de string de consulta ocorrem quando:

1. Os dados entram em um programa por uma fonte não confiável.

2. Os dados são usados para construir dinamicamente uma URL de consulta de Provedor de Conteúdo.

Provedores de conteúdo Android permitem que os desenvolvedores gravem consultas sem SQL simplesmente construindo URIs de provedor de conteúdo. URIs de consulta de provedores de conteúdo são vulneráveis a ataques de injeção e, portanto, os desenvolvedores devem evitar o uso da concatenação de strings com entradas de dados corrompidas para construir o URI, sem garantir que os metacaracteres estão devidamente validados ou codificados.

Exemplo 1: Considerando um aplicativo que expõe vários provedores de conteúdo em URIs:

content://my.authority/messagescontent://my.authority/messages/123content://my.authority/messages/deleted

Se os desenvolvedores construírem os URIs de consulta concatenando strings, os invasores poderão incluir barras no caminho ou outros metacaracteres de URI que modificarão o significado dessa consulta. No seguinte trecho de código, um invasor pode chamar content://my.authority/messages/deleted fornecendo um código msgId com o valor deleted:


// "msgId" is submitted by users
Uri dataUri = Uri.parse(WeatherContentProvider.CONTENT_URI + "/" + msgId);
Cursor wCursor1 = getContentResolver().query(dataUri, null, null, null, null);

References

[1] Standards Mapping - CIS Azure Kubernetes Service Benchmark 5.0

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

[3] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 5.0

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

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

[6] Standards Mapping - CIS Kubernetes Benchmark complete

[7] Standards Mapping - Common Weakness Enumeration CWE ID 89

[8] Standards Mapping - Common Weakness Enumeration Top 25 2019 [6] CWE ID 089

[9] Standards Mapping - Common Weakness Enumeration Top 25 2020 [6] CWE ID 089

[10] Standards Mapping - Common Weakness Enumeration Top 25 2021 [6] CWE ID 089

[11] Standards Mapping - Common Weakness Enumeration Top 25 2022 [3] CWE ID 089

[12] Standards Mapping - Common Weakness Enumeration Top 25 2023 [3] CWE ID 089

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

[14] Standards Mapping - FIPS200 SI

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

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

[17] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-10 Information Input 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 - OWASP Application Security Verification Standard 4.0 5.3.4 Output Encoding and Injection Prevention Requirements (L1 L2 L3), 5.3.5 Output Encoding and Injection Prevention Requirements (L1 L2 L3)

[25] Standards Mapping - OWASP Mobile 2014 M7 Client Side Injection

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

[27] Standards Mapping - OWASP Mobile Application Security Verification Standard 2.0 MASVS-CODE-4

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

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

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

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

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

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

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

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

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

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

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

[39] Standards Mapping - SANS Top 25 2009 Insecure Interaction - CWE ID 089

[40] Standards Mapping - SANS Top 25 2010 Insecure Interaction - CWE ID 089

[41] Standards Mapping - SANS Top 25 2011 Insecure Interaction - CWE ID 089

[42] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3510 CAT I, APP3540.1 CAT I, APP3540.3 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3510 CAT I, APP3540.1 CAT I, APP3540.3 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3510 CAT I, APP3540.1 CAT I, APP3540.3 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3510 CAT I, APP3540.1 CAT I, APP3540.3 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3510 CAT I, APP3540.1 CAT I, APP3540.3 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3510 CAT I, APP3540.1 CAT I, APP3540.3 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3510 CAT I, APP3540.1 CAT I, APP3540.3 CAT II

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[63] Standards Mapping - Web Application Security Consortium Version 2.00 SQL Injection (WASC-19)

[64] Standards Mapping - Web Application Security Consortium 24 + 2 SQL Injection

desc.dataflow.java.content_provider_uri_injection