Reino: API Abuse

Un API es un contrato entre un autor de llamada y un receptor de llamada. Las formas de abuso de API más comunes los produce el autor de llamada cuando no consigue atender su fin de este contrato. Por ejemplo, si un programa no consigue llamar chdir() después de llamar chroot(), se viola el contrato que especifica cómo cambiar el directorio de origen activo de una forma segura. Otro buen ejemplo de un abuso de manual es esperar que el receptor devuelva una información de DNS de confianza al autor de llamada. En este caso, el autor de llamada abusa el API del receptor haciendo determinadas suposiciones sobre su comportamiento (que el valor de retorno se puede usar con fines de autenticación). También se puede violar el contrato entre el autor de llamada y el receptor desde el otro lado. Por ejemplo, si un codificador envía SecureRandom y devuelve un valor no aleatorio, se viola el contrato.

Often Misused: Exception Handling

C/C++

Abstract

La función _alloca() puede lanzar una excepción de desbordamiento de pila, que podría ocasionar el bloqueo del programa.

Explanation

La función _alloca() asigna memoria en la pila. Si una solicitud de asignación es demasiado grande para el espacio de pila disponible, _alloca() lanza una excepción. Si la excepción no se detecta, el programa se bloquea, con la posibilidad de que se habilite un ataque por denegación de servicio.
_alloca() está en desuso desde Microsoft Visual Studio 2005(R). Se ha sustituido por _alloca_s(), más seguro.

References

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

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

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

[4] Standards Mapping - CIS Google Kubernetes Engine Benchmark confidentiality

[5] Standards Mapping - CIS Kubernetes Benchmark partial

[6] Standards Mapping - Common Weakness Enumeration CWE ID 248

[7] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-001094

[8] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data

[9] Standards Mapping - Motor Industry Software Reliability Association (MISRA) C Guidelines 2012 Rule 1.3

[10] Standards Mapping - NIST Special Publication 800-53 Revision 4 SC-5 Denial of Service Protection (P1)

[11] Standards Mapping - NIST Special Publication 800-53 Revision 5 SC-5 Denial of Service Protection

[12] Standards Mapping - OWASP Top 10 2004 A7 Improper Error Handling

[13] Standards Mapping - OWASP Top 10 2007 A6 Information Leakage and Improper Error Handling

[14] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.7

[15] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.3.1.2, Requirement 6.5.6

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

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

[18] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.5

[19] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.5

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

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

[22] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 3.6 - Sensitive Data Retention

[23] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 3.6 - Sensitive Data Retention, Control Objective B.3.2 - Terminal Software Attack Mitigation

[24] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 3.6 - Sensitive Data Retention, Control Objective B.3.2 - Terminal Software Attack Mitigation

[25] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3120 CAT II

[26] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3120 CAT II

[27] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3120 CAT II

[28] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3120 CAT II

[29] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3120 CAT II

[30] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3120 CAT II

[31] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3120 CAT II

[32] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002400 CAT II

[33] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002400 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002400 CAT II

[35] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002400 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002400 CAT II

[37] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002400 CAT II

[38] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002400 CAT II

[39] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002400 CAT II

[40] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002400 CAT II

[41] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002400 CAT II

[42] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002400 CAT II

[43] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002400 CAT II

[44] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002400 CAT II

[45] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002400 CAT II

desc.semantic.cpp.often_misused_exception_handling._alloca