Reino: Environment

Esta seção contém tudo o que fica fora do código-fonte, porém que é essencial para a segurança do produto que está sendo criado. Como os problemas tratados neste domínio não são diretamente relacionados com o código-fonte, nós o separamos dos demais domínios.

OpenAPI Misconfiguration: Empty Operation Security Requirement

JSON
YAML

Abstract

A especificação do OpenAPI inclui uma definição security vazia para uma operação da API.

Explanation

As operações da API definem os requisitos de segurança para informar os consumidores da API sobre os parâmetros de autenticação e autorização necessários para invocá-los com sucesso.

As operações que incluem uma definição security vazia podem permitir que invasores interajam com endpoints de API confidenciais e executem ações que devem ser restritas a contas de usuário específicas com privilégios explícitos.

Exemplo 1: A especificação do OpenAPI a seguir configura uma definição security vazia para uma operação confidencial. Isso substitui os requisitos de segurança definidos globalmente e torna a operação createUsers vulnerável a acesso não autorizado e não autenticado.


{
    "openapi": "3.0.0",
    "info": {
     ...
    },    
    "paths": {
      "/users": {
        "post": {
          "security": [],
          "summary": "Create a user",
          "operationId": "createUsers",
         ...
        }
    ...
    }
}

References

[1] OpenAPI Initiative OpenAPI Specification v3.1.0 - 4.8.30 Security Requirement Object

[2] OpenAPI Initiative OpenAPI Specification v3.1.0 - 4.8.10 Operation Object

[3] Standards Mapping - Common Weakness Enumeration CWE ID 284, CWE ID 359

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

[5] Standards Mapping - Common Weakness Enumeration Top 25 2020 [7] CWE ID 200

[6] Standards Mapping - Common Weakness Enumeration Top 25 2021 [20] CWE ID 200

[7] Standards Mapping - Common Weakness Enumeration Top 25 2024 [17] CWE ID 200

[8] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-002475

[9] Standards Mapping - FIPS200 CM

[10] Standards Mapping - General Data Protection Regulation (GDPR) Insufficient Data Protection

[11] Standards Mapping - NIST Special Publication 800-53 Revision 4 SC-28 Protection of Information at Rest (P1)

[12] Standards Mapping - NIST Special Publication 800-53 Revision 5 SC-28 Protection of Information at Rest

[13] Standards Mapping - OWASP API 2023 API5 Broken Function Level Authorization

[14] Standards Mapping - OWASP Application Security Verification Standard 4.0 1.4.2 Access Control Architectural Requirements (L2 L3), 1.4.4 Access Control Architectural Requirements (L2 L3), 8.3.4 Sensitive Private Data (L1 L2 L3), 10.2.1 Malicious Code Search (L2 L3)

[15] Standards Mapping - OWASP Mobile 2014 M2 Insecure Data Storage

[16] Standards Mapping - OWASP Top 10 2004 A8 Insecure Storage

[17] Standards Mapping - OWASP Top 10 2007 A6 Information Leakage and Improper Error Handling

[18] Standards Mapping - OWASP Top 10 2010 A6 Security Misconfiguration, A7 Insecure Cryptographic Storage, A8 Failure to Restrict URL Access

[19] Standards Mapping - OWASP Top 10 2013 A6 Sensitive Data Exposure

[20] Standards Mapping - OWASP Top 10 2017 A3 Sensitive Data Exposure

[21] Standards Mapping - OWASP Top 10 2021 A01 Broken Access Control

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 8.4

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.6, Requirement 8.4

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.4

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.2.1

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.2.1

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.2.1

[28] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 3.2, Requirement 3.4, Requirement 4.2, Requirement 6.5.5, Requirement 8.2.1

[29] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 3.3.1, Requirement 3.5.1, Requirement 4.2.2, Requirement 6.2.4, Requirement 8.3.1

[30] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 3.3.1, Requirement 3.3.2, Requirement 3.3.3, Requirement 3.5.1, Requirement 4.2.2, Requirement 6.2.4, Requirement 8.3.1

[31] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 3.3 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection

[32] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 3.3 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection

[33] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 3.3 - Sensitive Data Retention, Control Objective 6.1 - Sensitive Data Protection

[34] Standards Mapping - SANS Top 25 2010 Porous Defenses - CWE ID 863

[35] Standards Mapping - SANS Top 25 2011 Porous Defenses - CWE ID 863

[36] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3210.1 CAT II, APP3310 CAT I, APP3340 CAT I

[37] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3210.1 CAT II, APP3340 CAT I

[38] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3210.1 CAT II, APP3340 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3210.1 CAT II, APP3340 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3210.1 CAT II, APP3340 CAT I

[41] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3210.1 CAT II, APP3340 CAT I

[42] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3210.1 CAT II, APP3340 CAT I

[43] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002340 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002340 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002340 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002340 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002340 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002340 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002340 CAT II

[50] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002340 CAT II

[51] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002340 CAT II

[52] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002340 CAT II

[53] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002340 CAT II

[54] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002340 CAT II

[55] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002340 CAT II

[56] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002340 CAT II

[57] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002340 CAT II

[58] Standards Mapping - Security Technical Implementation Guide Version 6.2 APSC-DV-002340 CAT II

[59] Standards Mapping - Web Application Security Consortium Version 2.00 Information Leakage (WASC-13)

[60] Standards Mapping - Web Application Security Consortium 24 + 2 Information Leakage

desc.configuration.json.openapi_misconfiguration_empty_operation_security_requirement

Abstract

A especificação do OpenAPI inclui uma definição security vazia para uma operação da API.

Explanation


openapi: 3.0.0
info:
...
paths:
  /users:
    post:
      operationId: createUsers
      security: []
      responses:
        '201':
          ...