Kingdom: Environment
This section includes everything that is outside of the source code but is still critical to the security of the product that is being created. Because the issues covered by this kingdom are not directly related to source code, we separated it from the rest of the kingdoms.
Insecure Deployment: OpenSSL
Abstract
Deploying vulnerable versions of the OpenSSL library can enable an attacker to intercept and hijack secure SSL/TLS communication.
Explanation
OpenSSL is a popular third-party library used to encrypt network traffic. Depending on the version used, it might contain high profile vulnerabilities such as Heartbleed, ChangeCipherSpec injection, and incorrectly implemented Anonymous Elliptic Curve Diffie-Hellman (AECDH) ciphersuite. An application environment deployed with a vulnerable version of OpenSSL might be subjected to critical security threats including, but not limited to, denial of service, sensitive information disclosure, and unauthorized access to past encrypted information.
References
[1] Standards Mapping - Common Weakness Enumeration CWE ID 119, CWE ID 327
[2] Standards Mapping - Common Weakness Enumeration Top 25 2019 [1] CWE ID 119
[3] Standards Mapping - Common Weakness Enumeration Top 25 2020 [5] CWE ID 119
[4] Standards Mapping - Common Weakness Enumeration Top 25 2021 [17] CWE ID 119
[5] Standards Mapping - Common Weakness Enumeration Top 25 2022 [19] CWE ID 119
[6] Standards Mapping - Common Weakness Enumeration Top 25 2023 [17] CWE ID 119
[7] Standards Mapping - Common Weakness Enumeration Top 25 2024 [12] CWE ID 020, [20] CWE ID 119
[8] Standards Mapping - General Data Protection Regulation (GDPR) Insufficient Data Protection
[9] Standards Mapping - NIST Special Publication 800-53 Revision 4 SI-2 Flaw Remediation (P1)
[10] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-2 Flaw Remediation
[11] Standards Mapping - OWASP Application Security Verification Standard 4.0 2.6.3 Look-up Secret Verifier Requirements (L2 L3), 2.9.3 Cryptographic Software and Devices Verifier Requirements (L2 L3), 6.2.1 Algorithms (L1 L2 L3), 6.2.2 Algorithms (L2 L3), 8.3.7 Sensitive Private Data (L2 L3), 9.1.2 Communications Security Requirements (L1 L2 L3), 9.1.3 Communications Security Requirements (L1 L2 L3)
[12] Standards Mapping - OWASP Mobile 2024 M2 Inadequate Supply Chain Security
[13] Standards Mapping - OWASP Top 10 2013 A5 Security Misconfiguration
[14] Standards Mapping - OWASP Top 10 2021 A06 Vulnerable and Outdated Components
[15] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.2, Requirement 6.5.6
[16] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.2, Requirement 6.5.6
[17] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.2, Requirement 6.5.6
[18] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4, Requirement 6.3.3
[19] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 6.2.4, Requirement 6.3.3
[20] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 10.2 - Threat and Vulnerability Management
[21] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 10.2 - Threat and Vulnerability Management
[22] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 10.2 - Threat and Vulnerability Management, Control Objective C.1.6 - Web Software Components & Services
[23] Standards Mapping - SANS Top 25 2011 Porous Defenses - CWE ID 327
[24] Standards Mapping - Web Application Security Consortium Version 2.00 Information Leakage (WASC-13)
desc.dynamic.xtended_preview.insecure_deployment_openssl