Skip to content
OpenAdvisories

Weakness (CWE)

CWE-242: Use of Inherently Dangerous Function

Base Draft

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

How to prevent it (2 mitigations)

  1. 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]

  2. Testing

    Use grep or static analysis tools to spot usage of dangerous functions.

Source: MITRE CWE-242

All Critical High Medium Low Exploited only Public exploit

1 result · Clear filters · Feed

  • Medium —
    CVE-2017-0904

    private_address_check vulnerable to bypass of Resolv.getaddresses method

    The private_address_check ruby gem before 0.4.0 is vulnerable to a bypass due to use of Ruby's Resolv.getaddresses method, which is OS-dependent and should not be relied upon for security measures, such as when used to blacklist private network addresses to p…

    jtdowney private_address_check ruby gem private_address_check RubyGems