界: API Abuse

API 就像是呼叫者與被呼叫者之間簽訂的規定。最常見的 API 濫用形式是由呼叫者這一當事方未能遵守此規定所造成的。例如，如果程式在呼叫 chroot() 後無法呼叫 chdir()，即違反規範如何以安全方式變更使用中根目錄的規定。程式庫濫用的另一個好例子是期待被呼叫者向呼叫者傳回值得信賴的 DNS 資訊。在這種情況下，呼叫者是透過對其行為做出某些假設 (傳回值可用於驗證目的) 來濫用被呼叫者 API。另一方也可能違反呼叫者與被呼叫者間的規定。例如，如果編碼器衍生出子類別 SecureRandom 並傳回一個非隨機值，則違反了規定。

Often Misused: Privilege Management

Abstract

沒有堅守最小權限的原則，將有可能因其他弱點而擴大系統的風險。

Explanation

使用 root 權限來執行程式，已經造成了無數的 Unix 安全災難。仔細的檢查您的程式授予的權限是否會引起安全問題是十分重要的，而把那些被授予權限的程式及時撤銷權限也是同等重要，才能把那些弱點引起的破壞控制到最小。

Privilege Management 函數有時會以一些不明顯的方式執行，而且在不同的平台上面會有較大差異。當你把一個非 root 使用者轉換為另外一個時，這種差異會尤其明顯。

訊號處理常式以及產生的處理會在所有處理的權限下執行，所以如果處理以 root 權限執行，當訊號發生或執行子處理時，該訊號處理常式或者子處理將會以 Root 權限執行。這樣攻擊者將有可能利用這一點來擴大弱點造成的破壞。

References

[1] H. Chen, D. Wagner, and D. Dean. Setuid Demystified. 11th USENIX Security Symposium

[2] B. Chess and J. West, Secure Programming with Static Analysis. Boston, MA: Addison-Wesley, 2007.

[3] Standards Mapping - Common Weakness Enumeration CWE ID 250

[4] Standards Mapping - Common Weakness Enumeration Top 25 2023 [22] CWE ID 269

[5] Standards Mapping - Common Weakness Enumeration Top 25 2024 [15] CWE ID 269

[6] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-000345, CCI-000381, CCI-002233, CCI-002235

[7] Standards Mapping - General Data Protection Regulation (GDPR) Access Violation

[8] Standards Mapping - NIST Special Publication 800-53 Revision 4 AC-6 Least Privilege (P1), CM-5 Access Restrictions for Change (P1), CM-7 Least Functionality (P1), IA-5 Authenticator Management (P1)

[9] Standards Mapping - NIST Special Publication 800-53 Revision 5 AC-6 Least Privilege, CM-5 Access Restrictions for Change, CM-7 Least Functionality, IA-5 Authenticator Management

[10] Standards Mapping - OWASP API 2023 API1 Broken Object Level Authorization

[11] Standards Mapping - OWASP Application Security Verification Standard 4.0 1.2.1 Authentication Architectural Requirements (L2 L3), 10.2.2 Malicious Code Search (L2 L3)

[12] Standards Mapping - OWASP Mobile 2014 M5 Poor Authorization and Authentication

[13] Standards Mapping - OWASP Mobile 2024 M3 Insecure Authentication/Authorization

[14] Standards Mapping - OWASP Mobile Application Security Verification Standard 2.0 MASVS-AUTH-1

[15] Standards Mapping - OWASP Top 10 2021 A04 Insecure Design

[16] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 7.1.1

[17] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 7.1.1

[18] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 7.1.2

[19] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 7.1.2

[20] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 7.1.2

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 7.1.2

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 7.2.2

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 7.2.2

[24] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 5.4 - Authentication and Access Control

[25] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 5.4 - Authentication and Access Control

[26] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 5.4 - Authentication and Access Control, Control Objective C.2.3 - Web Software Access Controls

[27] Standards Mapping - SANS Top 25 2009 Porous Defenses - CWE ID 250

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

[29] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3500 CAT II

[30] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3500 CAT II

[31] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3500 CAT II

[32] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3500 CAT II

[33] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3500 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3500 CAT II

[35] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3500 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[37] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[38] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[39] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[40] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II, APSC-DV-001795 CAT II, APSC-DV-002960 CAT II

[50] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II, APSC-DV-001795 CAT II, APSC-DV-002960 CAT II

[51] Standards Mapping - Web Application Security Consortium Version 2.00 Insufficient Authorization (WASC-02)

[52] Standards Mapping - Web Application Security Consortium 24 + 2 Insufficient Authorization

desc.semantic.cpp.often_misused_privilege_management.setuid

Abstract

沒有堅守最小權限的原則，將有可能因其他弱點而擴大系統的風險。

Explanation

使用 root 權限來執行程式，已經造成了無數的 Unix 安全災難。仔細檢閱程式授予的權限是否會引起安全問題十分重要，而把那些被授予權限的程式及時撤銷權限也是同等重要，才能把那些弱點引起的破壞控制到最小。

Privilege Management 函數有時會以一些不明顯的方式執行，而且在不同的平台上面會有較大差異。當您把一個非 root 使用者轉換為其他使用者時，這種差異會尤其明顯。

訊號處理常式以及產生的程序會在所有程序的權限下執行，因此，如果程序以 root 權限執行，當訊號觸發或執行子程序時，該訊號處理常式或子程序將會以 Root 權限執行。攻擊者有可能利用這一點來擴大弱點造成的破壞。

References

[1] H. Chen, D. Wagner, and D. Dean. Setuid Demystified. 11th USENIX Security Symposium

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

[3] Standards Mapping - Common Weakness Enumeration Top 25 2023 [22] CWE ID 269

[4] Standards Mapping - Common Weakness Enumeration Top 25 2024 [15] CWE ID 269

[5] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-000345, CCI-000381, CCI-002233, CCI-002235

[6] Standards Mapping - General Data Protection Regulation (GDPR) Access Violation

[7] Standards Mapping - NIST Special Publication 800-53 Revision 4 AC-6 Least Privilege (P1), CM-5 Access Restrictions for Change (P1), CM-7 Least Functionality (P1), IA-5 Authenticator Management (P1)

[8] Standards Mapping - NIST Special Publication 800-53 Revision 5 AC-6 Least Privilege, CM-5 Access Restrictions for Change, CM-7 Least Functionality, IA-5 Authenticator Management

[9] Standards Mapping - OWASP API 2023 API1 Broken Object Level Authorization

[10] Standards Mapping - OWASP Application Security Verification Standard 4.0 1.2.1 Authentication Architectural Requirements (L2 L3), 10.2.2 Malicious Code Search (L2 L3)

[11] Standards Mapping - OWASP Mobile 2014 M5 Poor Authorization and Authentication

[12] Standards Mapping - OWASP Mobile 2024 M3 Insecure Authentication/Authorization

[13] Standards Mapping - OWASP Mobile Application Security Verification Standard 2.0 MASVS-AUTH-1

[14] Standards Mapping - OWASP Top 10 2021 A04 Insecure Design

[15] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 7.1.1

[16] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 7.1.1

[17] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 7.1.2

[18] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 7.1.2

[19] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 7.1.2

[20] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 7.1.2

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 7.2.2

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 7.2.2

[23] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 5.4 - Authentication and Access Control

[24] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 5.4 - Authentication and Access Control

[25] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 5.4 - Authentication and Access Control, Control Objective C.2.3 - Web Software Access Controls

[26] Standards Mapping - SANS Top 25 2009 Porous Defenses - CWE ID 250

[27] Standards Mapping - SANS Top 25 2011 Porous Defenses - CWE ID 250

[28] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3500 CAT II

[29] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3500 CAT II

[30] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3500 CAT II

[31] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3500 CAT II

[32] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3500 CAT II

[33] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3500 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3500 CAT II

[35] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[37] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[38] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[39] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[40] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[46] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[47] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II

[48] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II, APSC-DV-001795 CAT II, APSC-DV-002960 CAT II

[49] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-000500 CAT II, APSC-DV-000510 CAT I, APSC-DV-001500 CAT II, APSC-DV-001795 CAT II, APSC-DV-002960 CAT II

[50] Standards Mapping - Web Application Security Consortium Version 2.00 Insufficient Authorization (WASC-02)

[51] Standards Mapping - Web Application Security Consortium 24 + 2 Insufficient Authorization

desc.semantic.golang.often_misused_privilege_management

Abstract

沒有堅守最小權限的原則，將有可能因其他弱點而擴大系統的風險。

Explanation

使用 root 權限來執行程式，已經造成了無數的 Unix 安全災難。仔細地檢查您的程式授予的權限是否會引起安全問題是十分重要的，而把那些被授予權限的程式及時撤銷權限也是同等重要，才能把那些弱點引起的破壞控制到最小。

Privilege Management 函數有時會以一些不明顯的方式執行，而且在不同的平台上面會有較大差異。當您把一個非 root 使用者轉換為其他使用者時，這種差異會尤其明顯。

訊號處理常式以及產生的程序會在所有程序的權限下執行，因此，如果程序以 root 權限執行，當訊號觸發或執行子程序時，該訊號處理常式或子程序將會以 Root 權限執行。攻擊者將有可能利用這一點來擴大弱點造成的破壞。