Reino: API Abuse

Uma API é um contrato entre quem chama e o que se chama. As formas mais comuns de abuso de API ocorrem quando o responsável pela chamada não respeita sua parte do contrato. Por exemplo, se um programa não chama chdir() após chamar chroot(), ele viola o contrato que especifica como alterar o diretório raiz ativo de forma segura. Outro bom exemplo de abuso de biblioteca é esperar que o elemento chamado retorne informações confiáveis de DNS ao responsável pela chamada. Nesse caso, o responsável pela chamada abusa a API do elemento chamado ao fazer certas suposições sobre seu comportamento (isto é, que o valor de retorno pode ser usado para fins de autenticação). A outra parte também pode violar o contrato entre quem chama e o que se chama. Por exemplo, se um programador definir SecureRandom como subclasse e retornar um valor não aleatório, o contrato será violado.

Often Misused: Privilege Management

Abstract

A não aderência ao princípio do menor privilégio amplia o risco apresentado por outras vulnerabilidades.

Explanation

Programas que são executados com privilégios root causaram inúmeras catástrofes de segurança no Unix. É imperativo que você analise programas privilegiados cuidadosamente em busca de todos os tipos de problemas de segurança, mas é igualmente importante que esses programas privilegiados retornem a estado sem privilégios o mais rápido possível, a fim de limitar a quantidade de danos que uma vulnerabilidade despercebida pode ser capaz de causar.

Funções de gerenciamento de privilégios podem comportar-se de maneiras menos do que óbvias e têm peculiaridades diferentes dependendo da plataforma. Essas inconsistências são particularmente evidentes quando você está fazendo a transição de um usuário não root para outro.

Manipuladores de sinais e processos gerados são executados no privilégio do processo proprietário e, portanto, se um processo estiver em execução como root quando um sinal for acionado ou um subprocesso for executado, o manipulador de sinais ou subprocesso operará com privilégios de root. Um invasor pode ser capaz de aproveitar esses privilégios elevados para causar ainda mais danos.

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

Não respeitar o princípio de privilégio mínimo amplifica consideravelmente o risco relacionado com outras vulnerabilidades.

Explanation

Programas executados com privilégios de root causaram inúmeros desastres de segurança de Unix. É imperativo que você revise atentamente os programas com privilégios em relação a todos os tipos de problemas de segurança. É igualmente importante que os programas com privilégios retornem a um estado sem privilégios o mais rápido possível para limitar os danos que uma vulnerabilidade não remediada pode causar.

As funções de gestão de privilégios podem se comportar de formas pouco óbvias e possuem peculiaridades específicas em diferentes plataformas. Tais inconsistências são especialmente notáveis ao passar de um usuário não root a outro.

Manipuladores de sinais e processos gerados são executados de acordo com o privilégio do processo principal. Assim, se um processo estiver sendo executado como root quando um sinal for disparado ou quando um subprocesso for executado, o manipulador de sinais ou o subprocesso operará com privilégios de root. Um invasor pode aproveitar esses privilégios elevados para causar ainda mais danos.

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