CyberSecBulletin

Use of Inherently Dangerous Function

CWE-242

The product calls a function that can never be guaranteed to work safely, regardless of how it is used.

We track 6 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.6.

How this weakness is prevented

  • 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.
  • Testing: Use grep or static analysis tools to spot usage of dangerous functions.

Latest Use of Inherently Dangerous Function vulnerabilities