Use of Prohibited Code

Opis

The product uses a function, library, or third party component that has been explicitly prohibited, whether by the developer or the customer.

The developer - or customers - may wish to restrict or eliminate use of a function, library, or third party component for any number of reasons, including real or suspected vulnerabilities; difficulty to use securely; export controls or license requirements; obsolete or poorly-maintained code; internal code being scheduled for deprecation; etc.

To reduce risk of vulnerabilities, the developer might maintain a list of "banned" functions that programmers must avoid using because the functions are difficult or impossible to use securely. This issue can also make the product more costly and difficult to maintain.

Skutki

• Other

  Reduce Maintainability

Zapobieganie

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

Przykłady podatności

• CVE-2007-1470 Library has multiple buffer overflows using sprintf() and strcpy()
• CVE-2007-4004 FTP client uses inherently insecure gets() function and is setuid root on some systems, allowing buffer overflow

Słabość nadrzędna

• CWE-710 Improper Adherence to Coding Standards

Słabości podrzędne

• CWE-242 Use of Inherently Dangerous Function
• CWE-676 Use of Potentially Dangerous Function

Kiedy powstaje

• Implementation

Dotyczy

Not Language-Specific

Źródła

1. Security Development Lifecycle (SDL) Banned Function Calls — Michael Howard, 2011
2. Microsoft's Free Security Tools - banned.h — Tim Rains, 2012
3. Writing Secure Code — Michael Howard, David LeBlanc, Microsoft Press, 2002