界: Security Features

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

Weak Cryptographic Hash: Null Salt

PHP
Python

Abstract

null salt (NULL) 背离其预期目标，可能会削弱系统安全性，一旦出现安全问题将无法轻易修正。

Explanation

使用 null salt (NULL) 绝非一个好方法。不仅 nullsalt 背离其预期目标，而且该项目的所有开发人员都可以查看 salt。这使得修复问题变得极其困难，因为一旦该代码投入使用，则无法轻易更改该 salt。如果攻击者知道 salt 的值，他们就可以计算出该应用程序的“彩虹表”，并轻松地确定散列值。

示例 1：以下代码使用了 null salt：


...
define('SECURE_AUTH_SALT', NULL);
...

此代码成功运行，但有权访问此代码的任何人都可以查看 salt。一旦程序发布，可能无法更改 null salt。雇员可以利用手中掌握的信息访问权限入侵系统。

References

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

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

[3] Standards Mapping - FIPS200 MP

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

[5] Standards Mapping - NIST Special Publication 800-53 Revision 4 AU-10 Non-Repudiation (P2), SC-13 Cryptographic Protection (P1), SC-23 Session Authenticity (P1)

[6] Standards Mapping - NIST Special Publication 800-53 Revision 5 AU-10 Non-Repudiation, SC-13 Cryptographic Protection, SC-23 Session Authenticity

[7] Standards Mapping - OWASP Application Security Verification Standard 4.0 2.4.1 Credential Storage Requirements (L2 L3), 2.4.2 Credential Storage Requirements (L2 L3), 2.4.5 Credential Storage Requirements (L2 L3), 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)

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

[9] Standards Mapping - OWASP Mobile 2024 M10 Insufficient Cryptography

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

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

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

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

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

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

[16] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.8

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

[18] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.3

[19] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.3

[20] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.3

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.3

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.3

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 3.3.2, Requirement 3.3.3, Requirement 3.5.1, Requirement 6.2.4

[25] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 7.1 - Use of Cryptography, Control Objective 7.4 - Use of Cryptography

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

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

[28] Standards Mapping - SANS Top 25 2011 Porous Defenses - CWE ID 759

[29] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3150.1 CAT II

[30] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3150.1 CAT II

[31] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3150.1 CAT II

[32] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3150.1 CAT II

[33] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3150.1 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3150.1 CAT II

[35] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3150.1 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[37] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[38] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[39] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[40] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-000590 CAT II, APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II, APSC-DV-002290 CAT II

[50] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-000590 CAT II, APSC-DV-002010 CAT II, APSC-DV-002020 CAT II, APSC-DV-002030 CAT II, APSC-DV-002290 CAT II

desc.semantic.php.weak_cryptographic_hash_null_salt

Abstract

null salt (None) 会背离其自己的目标，可能会削弱系统安全性，一旦出现安全问题将无法轻易修正。

Explanation

使用 null salt (None) 绝非一个好方法。null salt 不仅会背离自己的初衷，还允许所有的项目开发人员查看该 salt，并使解决此问题变得极其困难。一旦该代码投入使用，则无法轻易更改该 salt。如果攻击者知道 salt 的值，他们就可以计算出该应用程序的“彩虹表”，并更轻松地确定散列值。

示例 1：以下代码会使用 null salt (None)：


from django.utils.crypto import salted_hmac
...
hmac = salted_hmac(value, None).hexdigest()
...

此代码将成功运行，但有权访问此代码的任何人都可以访问 salt。一旦程序发布，可能无法更改 null salt。雇员可以利用手中掌握的信息访问权限入侵系统。