CWE-676 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.

• Other: Varies by Context, Quality Degradation, Unexpected State — If the function is used incorrectly, then it could result in security problems.

• [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]

• Automated Static Analysis - Binary or Bytecode: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Bytecode Weakness Analysis - including disassembler + source code weakness analysis • Binary Weakness Analysis - including disassembler + source code weakness analysis Cost effective for partial coverage: • Binary / Bytecode Quality Analysis • Binary / Bytecode simple extractor - strings, ELF readers, etc. • Manual Static Analysis - Binary or Bytecode: According to SOAR [REF-1479], the following detection techniques may be useful: Cost effective for partial coverage: • Binary / Bytecode disassembler - then use manual analysis for vulnerabilities & anomalies • Dynamic Analysis with Manual Results Interpretation: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Debugger Cost effective for partial coverage: • Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious • Manual Static Analysis - Source Code: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Manual Source Code Review (not inspections) Cost effective for partial coverage: • Focused Manual Spotcheck - Focused manual analysis of source • Automated Static Analysis - Source Code: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Source code Weakness Analyzer • Context-configured Source Code Weakness Analyzer Cost effective for partial coverage: • Warning Flags • Source Code Quality Analyzer • Automated Static Analysis: According to SOAR [REF-1479], the following detection techniques may be useful: Cost effective for partial coverage: • Origin Analysis • Architecture or Design Review: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Formal Methods / Correct-By-Construction • Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)

• 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() • CVE-2008-5005: Buffer overflow using strcpy()