CWE-676: Use of Potentially Dangerous Function | Mondoo Vulnerability Intelligence

CWE-676

BaseDraft

Use of Potentially Dangerous Function

The product invokes a potentially dangerous function that could introduce a vulnerability if it is used incorrectly, but the function can also be used safely.

7 linked vulnerabilities

1 related weaknesses

Build and Compilation

Implementation

Identify a list of prohibited API functions and prohibit developers from using these functions, providing safer alternatives. In some cases, automatic code analysis tools or the compiler can be instructed to spot use of prohibited functions, such as the "banned.h" include file from Microsoft's SDL. [REF-554] [REF-1009] [REF-7]

Other

Varies by Context

Quality Degradation

Unexpected State

If the function is used incorrectly, then it could result in security problems.

Automated Static Analysis - Binary or Bytecode

Effectiveness: High

According to SOAR [REF-1479], the following detection techniques may be useful:

Manual Static Analysis - Binary or Bytecode

Effectiveness: SOAR Partial

According to SOAR [REF-1479], the following detection techniques may be useful:

Binary / Bytecode disassembler - then use manual analysis for vulnerabilities & anomalies

Dynamic Analysis with Manual Results Interpretation

Effectiveness: High

According to SOAR [REF-1479], the following detection techniques may be useful:

Manual Static Analysis - Source Code

Effectiveness: High

According to SOAR [REF-1479], the following detection techniques may be useful:

Automated Static Analysis - Source Code

Effectiveness: High

According to SOAR [REF-1479], the following detection techniques may be useful:

Automated Static Analysis

Effectiveness: SOAR Partial

According to SOAR [REF-1479], the following detection techniques may be useful:

Origin Analysis

Architecture or Design Review

Effectiveness: High

According to SOAR [REF-1479], the following detection techniques may be useful:

Formal Methods / Correct-By-Construction
Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)

Modes of Introduction

Implementation

Related Weaknesses

CWE-1177ChildOf

Example CVEs (6)

CVE-2007-1470

Library has multiple buffer overflows using sprintf() and strcpy()

CVE-2009-3849

Buffer overflow using strcat()

CVE-2006-2114

Buffer overflow using strcpy()

CVE-2006-0963

Buffer overflow using strcpy()

CVE-2011-0712

Vulnerable use of strcpy() changed to use safer strlcpy()

External Links

MITRE CWE Database