Skip to content

CWE-676: Use of Potentially Dangerous Function

BaseLikelihood of exploit: High

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.

Consequences

  • Other: Varies by Context, Quality Degradation, Unexpected State

How to prevent it

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

Recent advisories

All advisories for CWE-676

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor