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.

Dynamic Code Evaluation: Unsafe YAML Deserialization

Abstract

Desserializar fluxos YAML controlados pelo usuário pode permitir que invasores executem código arbitrário no servidor, abusem da lógica do aplicativo e/ou provoquem uma negação de serviço.

Explanation

As bibliotecas de serialização YAML, que convertem gráficos de objetos em dados formatados YAML, podem incluir os metadados necessários para reconstruir os objetos de volta do fluxo YAML. Se os invasores puderem especificar as classes dos objetos a serem reconstruídos e forçar o aplicativo a executar setters arbitrários com dados controlados pelo usuário, eles poderão executar o código arbitrário durante a desserialização do fluxo YAML.

Exemplo: O exemplo a seguir desserializa uma string YAML não confiável usando o analisador YamlDotNet.


    var yamlString = getYAMLFromUser();

    // Setup the input
    var input = new StringReader(yamlString);

    // Load the stream
    var yaml = new YamlStream();
    yaml.Load(input);

References

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

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

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

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

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

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

[7] Standards Mapping - CIS Kubernetes Benchmark complete

[8] Standards Mapping - Common Weakness Enumeration CWE ID 502

[9] Standards Mapping - Common Weakness Enumeration Top 25 2019 [23] CWE ID 502

[10] Standards Mapping - Common Weakness Enumeration Top 25 2020 [21] CWE ID 502

[11] Standards Mapping - Common Weakness Enumeration Top 25 2021 [13] CWE ID 502

[12] Standards Mapping - Common Weakness Enumeration Top 25 2022 [12] CWE ID 502

[13] Standards Mapping - Common Weakness Enumeration Top 25 2023 [15] CWE ID 502

[14] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-001764, CCI-001774, CCI-002754

[15] Standards Mapping - FIPS200 SI

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

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

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

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

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

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

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

[23] Standards Mapping - OWASP Top 10 2017 A8 Insecure Deserialization

[24] Standards Mapping - OWASP Top 10 2021 A08 Software and Data Integrity Failures

[25] Standards Mapping - OWASP Application Security Verification Standard 4.0 1.5.2 Input and Output Architectural Requirements (L2 L3), 5.5.1 Deserialization Prevention Requirements (L1 L2 L3), 5.5.3 Deserialization Prevention Requirements (L1 L2 L3)

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

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

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

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

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

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

[32] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 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 3.1 Requirement 6.5.1

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

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

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

[39] 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, Control Objective C.3.5 - Web Software Attack Mitigation

[40] Standards Mapping - SANS Top 25 2009 Insecure Interaction - CWE ID 116

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

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

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

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

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

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

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

[48] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[49] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[50] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[51] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[52] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[53] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[54] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[55] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[56] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[57] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[58] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[59] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

[60] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-001480 CAT II, APSC-DV-001490 CAT II, APSC-DV-002560 CAT I

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

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

desc.dataflow.dotnet.dynamic_code_evaluation_unsafe_yaml_deserialization