界: 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 - Common Weakness Enumeration Top 25 2024 [14] CWE ID 287, [22] CWE ID 798

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

[9] Standards Mapping - FIPS200 IA

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

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

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

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

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

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

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

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

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

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

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

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

[22] Standards Mapping - OWASP Top 10 2021 A02 Cryptographic Failures

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[58] 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);
...

不僅任何有程式碼存取權的人都能夠確定這會根據 null 密碼引數產生一或多個加密金鑰，甚至任何人運用基本破解技術，也都極可能會成功取得權限以存取由違反規則的金鑰所保護的任何資源。如果攻擊者還能存取用於根據 null 密碼產生任何金鑰的 Salt 值，則破解那些金鑰就變得相當簡單了。程式發佈後，除非修補此程式，否則不能變更 null 密碼。若員工有此資訊的存取權，則可能會使用此資訊來進入並破壞系統。即使攻擊者僅有應用程式可執行檔的存取權，他們也可以擷取 null 密碼的使用證據。