界: Security Features

软件安全不是安全软件。此处我们关注的主题包括身份验证、Access Control、机密性、加密和权限管理。

Key Management: Null PBE Password

Abstract

如果生成和使用基于 null 密码的加密密钥，则可能会削弱系统安全性，一旦出现安全问题将无法轻易修正。

Explanation

将 null 值作为密码参数传递到基于加密密码的密钥派生函数绝非一个好方法。在这种情况下，生成的派生密钥将仅基于提供的 salt（使其强度显著减弱），并且修复该问题极其困难。一旦问题代码投入使用，除非对软件进行修补，否则通常无法更改 null 密码。如果受基于 null 密码的派生密钥保护的帐户遭到破坏，则系统所有者可能不得不在安全性和可用性之间进行选择。

示例 1：下列代码会将 null 值作为密码参数传递到基于加密密码的密钥派生函数中：


...
var encryptor = new StrongPasswordEncryptor();
var encryptedPassword = encryptor.encryptPassword(null);
...

不仅有权访问此代码的任何人可以确定它基于 null 密码参数生成一个或多个加密密钥，而且掌握基本破解技术的任何人更有可能成功访问任何受问题密钥保护的资源。如果攻击者还可以访问用于基于 null 密码生成任何密钥的 salt 值，则破解那些密钥就变得微不足道。一旦程序发布，除非修补该程序，否则可能无法更改 null 密码。雇员可以利用手中掌握的信息访问权限入侵系统。即使攻击者只能访问应用程序的可执行文件，他们也可以提取使用 null 密码的证据。

References

[1] Standards Mapping - Common Weakness Enumeration CWE ID 321

[2] Standards Mapping - Common Weakness Enumeration Top 25 2019 [13] CWE ID 287, [19] CWE ID 798

[3] Standards Mapping - Common Weakness Enumeration Top 25 2020 [14] CWE ID 287, [20] CWE ID 798

[4] Standards Mapping - Common Weakness Enumeration Top 25 2021 [14] CWE ID 287, [16] CWE ID 798

[5] Standards Mapping - Common Weakness Enumeration Top 25 2022 [14] CWE ID 287, [15] CWE ID 798

[6] Standards Mapping - Common Weakness Enumeration Top 25 2023 [13] CWE ID 287, [18] CWE ID 798

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

[8] Standards Mapping - FIPS200 IA

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

[10] Standards Mapping - NIST Special Publication 800-53 Revision 4 SC-12 Cryptographic Key Establishment and Management (P1), SC-13 Cryptographic Protection (P1)

[11] Standards Mapping - NIST Special Publication 800-53 Revision 5 SC-12 Cryptographic Key Establishment and Management, SC-13 Cryptographic Protection

[12] Standards Mapping - OWASP Application Security Verification Standard 4.0 2.6.2 Look-up Secret Verifier Requirements (L2 L3), 2.6.3 Look-up Secret Verifier Requirements (L2 L3), 2.7.1 Out of Band Verifier Requirements (L1 L2 L3), 2.7.2 Out of Band Verifier Requirements (L1 L2 L3), 2.7.3 Out of Band Verifier Requirements (L1 L2 L3), 2.8.4 Single or Multi Factor One Time Verifier Requirements (L2 L3), 2.8.5 Single or Multi Factor One Time Verifier Requirements (L2 L3), 2.9.1 Cryptographic Software and Devices Verifier Requirements (L2 L3), 2.10.2 Service Authentication Requirements (L2 L3), 2.10.4 Service Authentication Requirements (L2 L3), 3.5.2 Token-based Session Management (L2 L3), 3.7.1 Defenses Against Session Management Exploits (L1 L2 L3), 6.2.1 Algorithms (L1 L2 L3), 6.4.1 Secret Management (L2 L3), 6.4.2 Secret Management (L2 L3), 9.2.3 Server Communications Security Requirements (L2 L3), 10.2.3 Malicious Code Search (L3)

[13] Standards Mapping - OWASP Mobile 2014 M6 Broken Cryptography

[14] Standards Mapping - OWASP Mobile 2024 M1 Improper Credential Usage

[15] Standards Mapping - OWASP Mobile Application Security Verification Standard 2.0 MASVS-CRYPTO-2

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

[17] Standards Mapping - OWASP Top 10 2007 A8 Insecure Cryptographic Storage

[18] Standards Mapping - OWASP Top 10 2010 A7 Insecure Cryptographic Storage

[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 A02 Cryptographic Failures

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

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.3.1.3, Requirement 6.5.8, Requirement 8.4

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.3.1, Requirement 6.5.3, Requirement 8.4

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.3.1, Requirement 6.5.3, Requirement 8.2.1

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.3.1, Requirement 6.5.3, Requirement 8.2.1

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.3.1, Requirement 6.5.3, Requirement 8.2.1

[28] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.3.1, Requirement 6.5.3, Requirement 8.2.1

[29] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4, Requirement 6.5.3, Requirement 6.5.6, Requirement 8.3.2

[30] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 7.2 - Use of Cryptography

[31] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 7.2 - Use of Cryptography, Control Objective B.2.3 - Terminal Software Design

[32] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 7.2 - Use of Cryptography, Control Objective B.2.3 - Terminal Software Design

[33] Standards Mapping - SANS Top 25 2009 Porous Defenses - CWE ID 259

[34] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3210.1 CAT II, APP3350 CAT I

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

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

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

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

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

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

[41] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002010 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002010 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002010 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002010 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002010 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002010 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002010 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002010 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002010 CAT II

[50] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002010 CAT II

[51] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002010 CAT II

[52] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002010 CAT II

[53] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002010 CAT II

[54] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002010 CAT II

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

desc.semantic.java.key_management_null_pbe_password

Abstract

如果生成和使用基于 null 密码的加密密钥，则可能会削弱系统安全性，一旦出现安全问题将无法轻易修正。

Explanation


...
CCKeyDerivationPBKDF(kCCPBKDF2,
                     nil,
                     0,
                     salt,
                     saltLen
                     kCCPRFHmacAlgSHA256,
                     100000,
                     derivedKey,
                     derivedKeyLen);
...