界: 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 - CIS Azure Kubernetes Service Benchmark 1

[4] Standards Mapping - CIS Microsoft Azure Foundations Benchmark partial

[5] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 1

[6] Standards Mapping - CIS Amazon Web Services Foundations Benchmark 3

[7] Standards Mapping - CIS Google Kubernetes Engine Benchmark integrity

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

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

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

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

[12] Standards Mapping - NIST Special Publication 800-53 Revision 4 AC-6 Least Privilege (P1)

[13] Standards Mapping - NIST Special Publication 800-53 Revision 5 AC-6 Least Privilege

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

desc.semantic.cpp.often_misused_privilege_management.setuid

Abstract

未能遵循最小特权原则会增加其他漏洞带来的风险。

Explanation

以 root 权限运行的程序已导致了无数的 Unix 安全灾难。您必须仔细审查特权程序是否存在各种安全问题，但同样重要的是，特权程序应尽快恢复到非特权状态，以限制被忽略的漏洞可能造成的损害。

权限管理功能可能会以一些不太明显的方式运行，并且它们在不同平台上具有不同的特性。如果您从一个非 root 用户转换到另一个非 root 用户，这些不一致尤为明显。

信号处理程序和派生的流程以所拥有流程的权限运行，因此，如果在触发信号或执行子流程时某个流程以 root 身份运行，则信号处理程序或子流程将以 root 权限运行。攻击者可能会利用这些提升的权限进行进一步的破坏。

References

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

[2] Standards Mapping - CIS Azure Kubernetes Service Benchmark 1

[3] Standards Mapping - CIS Microsoft Azure Foundations Benchmark partial

[4] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 1

[5] Standards Mapping - CIS Amazon Web Services Foundations Benchmark 3

[6] Standards Mapping - CIS Google Kubernetes Engine Benchmark integrity

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

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

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

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

[11] Standards Mapping - NIST Special Publication 800-53 Revision 4 AC-6 Least Privilege (P1)

[12] Standards Mapping - NIST Special Publication 800-53 Revision 5 AC-6 Least Privilege

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[53] 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 权限运行。因此，攻击者有可能利用这些提高的权限来进行更严重的破坏。