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.

Dangerous Function: strcpy()

C/C++

Abstract

Nunca deben usarse las funciones que no se pueden utilizar con seguridad.

Explanation

Determinadas funciones se comportan de forma peligrosa independientemente de cómo se utilicen. Las funciones de esta categoría se implementaron a menudo sin tener en cuenta las cuestiones relativas a la seguridad.

References

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

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

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

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

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

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

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

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

[9] Standards Mapping - Motor Industry Software Reliability Association (MISRA) C++ Guidelines 2008 Rule 18-0-5

[10] Standards Mapping - NIST Special Publication 800-53 Revision 4 SI-16 Memory Protection (P1)

[11] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-16 Memory Protection

[12] Standards Mapping - OWASP Top 10 2004 A5 Buffer Overflow

[13] Standards Mapping - OWASP Mobile 2014 M7 Client Side Injection

[14] Standards Mapping - OWASP Mobile Application Security Verification Standard 2.0 MASVS-CODE-4

[15] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.5

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

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

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

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

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

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

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

[23] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 4.2 - Critical Asset Protection

[24] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 4.2 - Critical Asset Protection

[25] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 4.2 - Critical Asset Protection

[26] Standards Mapping - SANS Top 25 2011 Risky Resource Management - CWE ID 676

[27] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP2060.4 CAT II, APP3590.2 CAT I

[28] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP2060.4 CAT II, APP3590.2 CAT II

[29] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP2060.4 CAT II, APP3590.2 CAT II

[30] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP2060.4 CAT II, APP3590.2 CAT II

[31] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP2060.4 CAT II, APP3590.2 CAT II

[32] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP2060.4 CAT II, APP3590.2 CAT II

[33] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP2060.4 CAT II, APP3590.2 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002590 CAT I

[35] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002590 CAT I

[36] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002590 CAT I

[37] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002590 CAT I

[38] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002590 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002590 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002590 CAT I

[41] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002590 CAT I

[42] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002590 CAT I

[43] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002590 CAT I

[44] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002590 CAT I

[45] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002590 CAT I

[46] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002590 CAT I

[47] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002590 CAT I

[48] Standards Mapping - Web Application Security Consortium Version 2.00 Buffer Overflow (WASC-07)

[49] Standards Mapping - Web Application Security Consortium 24 + 2 Buffer Overflow

desc.semantic.cpp.dangerous_function_strcpy