계: Environment

이 섹션에는 소스 코드 외부에 있지만 제작 중인 제품의 보안에는 여전히 중요한 내용이 모두 포함되어 있습니다. 이 섹션에서 다루는 문제들은 소스 코드와 직접적으로 관련이 없기 때문에 나머지 섹션과 분리했습니다.

OpenAPI Misconfiguration: Optional Operation Security Requirement

JSON
YAML

Abstract

해당 OpenAPI 사양에는 API 작업의 보안이 선택 사항으로 설정되어 있습니다.

Explanation

API 작업에서는 API 소비자에게 API를 정상적으로 호출하려면 필요한 인증 및 권한 부여 매개 변수 정보를 제공하도록 하는 보안 요구사항을 정의합니다.

보안이 선택 사항으로 설정된 작업을 수행하는 경우 공격자가 중요한 API 끝점과 상호 작용하게 될 수 있습니다. 그러면 명시적 권한이 있는 특정 사용자 계정만 수행 가능하도록 제한해야 하는 작업을 수행할 수 있습니다.

예제 1: 다음 OpenAPI 사양에는 보안이 선택 사항으로 설정되어 있습니다. 중요한 작업의 security 정의 내에 비어 있는 {} 개체가 포함되어 있기 때문입니다. 이로 인해 전역적으로 정의된 보안 요구사항이 다시 정의되며, createUsers 작업이 미인증 무단 액세스에 취약해집니다.


{
    "openapi": "3.0.0",
    "info": {
     ...
    },    
    "paths": {
      "/users": {
        "post": {
           "security": [
            {},
            {
              "my_auth": [
                "write:users"
              ]
            }
          ],
          "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_optional_operation_security_requirement

Abstract

해당 OpenAPI 사양에는 API 작업의 보안이 선택 사항으로 설정되어 있습니다.

Explanation


openapi: 3.0.0
info:
...
paths:
  /users:
    post:
      operationId: createUsers
      security: 
      - {}
      - oauth_auth:
          - write:users
          - read:users
      responses:
        '201':
          ...