계: API Abuse

API는 호출자와 피호출자 간의 계약입니다. 가장 흔한 형태의 API 오용은 호출자가 이 계약에서 자신의 몫을 이행하지 못하기 때문에 발생합니다. 예를 들어, 프로그램이 chroot()를 호출한 후 chdir()을 호출하지 못하면 활성 루트 디렉터리를 안전하게 변경하는 방법을 지정하는 계약을 위반하는 것입니다. 라이브러리 오용의 또 다른 좋은 예는 피호출자가 호출자에게 신뢰할 만한 DNS 정보를 반환할 것으로 예상하는 것입니다. 이 경우, 호출자는 자신의 행동에 대해 특정한 가정을 함으로써(반환 값이 인증 목적으로 사용될 것으로 예상) 피호출자 API를 오용합니다. 다른 쪽에서 호출자-피호출자 계약을 위반할 수도 있습니다. 예를 들어, 코더가 하위 클래스 SecureRandom을 지정하고 임의 값이 아닌 값을 반환하는 경우 계약을 위반하는 것입니다.

Dangerous Function: strcpy()

C/C++

Abstract

안전하게 사용할 수 없는 함수는 사용하지 않는 것이 좋습니다.

Explanation

일부 함수는 사용 방법에 관계 없이 위험하게 동작합니다. 이 카테고리에 속하는 함수는 보안 문제를 고려하지 않고 구현된 것입니다.

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