界: Security Features

軟體安全性並非安全性軟體。我們關注驗證、Access Control、保密性、加密以及權限管理之類的主題。

Insecure Randomness: Weak Entropy Source

C/C++
Python

Abstract

隨機或虛擬亂數產生器依靠安全性低的複雜度來源。

Explanation

如果隨機或虛擬亂數產生器沒有可使用的適當複雜度來源，可能會導致阻斷服務攻擊，或是產生可預測的亂數序列。如果隨機或虛擬亂數產生器使用的複雜度來源已耗盡，則程式可能會暫停，甚至當機，進而導致阻斷服務攻擊。或者，隨機或虛擬亂數產生器會產生可預測的亂數。安全性低的隨機或虛擬亂數來源會導致弱點，例如易猜的臨時密碼、加密金鑰、階段作業劫持，以及 DNS 欺騙。

範例 1：以下程式碼使用系統時鐘做為複雜度來源：


    ...
    srand (time(NULL));
    r = (rand() % 6) + 1;
    ...

由於系統時鐘會產生可預測的值，因此並非理想的複雜度來源。其他的非硬體型隨機來源 (包括系統/輸入/輸出緩衝區、使用者/系統/硬體/網路序號或位址，以及使用者輸入) 亦是如此。

References

[1] Elaine Barker and John Kelsey NIST DRAFT Special Publication 800-90B: Recommendation for the Entropy Sources Used for Random Bit Generation NIST

[2] Standards Mapping - Common Weakness Enumeration CWE ID 331

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

[4] Standards Mapping - FIPS200 MP

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

[6] Standards Mapping - Motor Industry Software Reliability Association (MISRA) C Guidelines 2023 Rule 21.24

[7] Standards Mapping - NIST Special Publication 800-53 Revision 4 SC-13 Cryptographic Protection (P1)

[8] Standards Mapping - NIST Special Publication 800-53 Revision 5 SC-13 Cryptographic Protection

[9] Standards Mapping - OWASP Application Security Verification Standard 4.0 2.3.1 Authenticator Lifecycle Requirements (L1 L2 L3), 2.6.2 Look-up Secret Verifier Requirements (L2 L3), 3.2.2 Session Binding Requirements (L1 L2 L3), 3.2.4 Session Binding Requirements (L2 L3), 6.3.3 Random Values (L3)

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

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

[12] Standards Mapping - OWASP Mobile Application Security Verification Standard 2.0 MASVS-CRYPTO-1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[27] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 7.3 - Use of Cryptography, Control Objective B.2.4 - Terminal Software Design

[28] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 7.3 - Use of Cryptography, Control Objective B.2.4 - Terminal Software Design

[29] Standards Mapping - SANS Top 25 2009 Porous Defenses - CWE ID 330

[30] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3150.2 CAT II

[31] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3150.2 CAT II

[32] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3150.2 CAT II

[33] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3150.2 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3150.2 CAT II

[35] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3150.2 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3150.2 CAT II

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

desc.dataflow.cpp.insecure_randomness_weak_entropy_source

Abstract

隨機或虛擬亂數產生器依靠安全性低的複雜度來源。

Explanation

如果隨機或虛擬亂數產生器沒有可使用的適當複雜度來源，可能會導致阻斷服務攻擊，或是產生可預測的亂數序列。如果隨機或虛擬亂數產生器使用的複雜度來源已耗盡，則程式可能會暫停，甚至當機，進而導致阻斷服務攻擊。或者，隨機或虛擬亂數產生器會產生可預測的亂數。弱式亂數來源可能會導致弱點，例如，易猜的臨時密碼、可預測的加密金鑰、階段作業劫持以及 DNS 欺騙。

範例 1：以下程式碼使用系統時鐘做為複雜度來源：


...
import time
import random

random.seed(time.time())
...