界: Environment

本节包括的所有内容均与源代码无关，但对所创建产品的安全性仍然至关重要。因为本节涉及的问题与源代码没有直接关系，所以我们将它与其他章节分开。

OpenAPI Misconfiguration: Empty Global Security Requirement

JSON
YAML

Abstract

OpenAPI 规范定义了一个空的全局 security 定义。

Explanation

全局安全要求通知 API 使用者成功与 API 交互所需的身份验证和授权参数。

空的全局 security 定义可能使攻击者能够与敏感的 API 端点进行交互，并允许他们执行应仅限于具有显式权限的特定用户帐户的操作。

示例 1：以下 OpenAPI 规范声明了一个空的全局 security 定义。实现此规范的 API 可能容易受到对敏感操作的未经授权或未经身份验证的访问。


{
    "openapi" : "3.0.3",
    "info" : {
        "title" : "My API",
        "version" : "1.0.0"
    },
    "servers" : [ {
        "url" : "/"
    } ],
    "security" : [],
    ...
}

References

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

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

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

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

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

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

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

[8] Standards Mapping - FIPS200 CM

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

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

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

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

[13] 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)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

desc.configuration.json.openapi_misconfiguration_empty_global_security_requirement

Abstract

OpenAPI 规范定义了一个空的全局 security 定义。

Explanation


    openapi: 3.0.3
    info:
      title: My API
      version: 1.0.0
    security: