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

11 results · Feed

  • High 7.3

    Code execution in IBM Desktop App

    IBM Aspera Desktop App 1.0.5 through 1.0.19 can allow arbitrary code execution by loading DLL files at start-up.

  • High 8.8

    PostgreSQL libpq lo_* functions let server superuser overwrite client stack memory

    Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lseek64(), and lo_tell64() functions allows the server superuser to overwrite a client stack buffer with an arbitrarily-large response. Like ge…

  • High 7.8

    IBM Cognos Command Center code execution

    IBM Cognos Command Center 10.2.4.1 and 10.2.5 could allow a local user to execute arbitrary code on the system due to the use of unsafe use of the BinaryFormatter function.

  • High 8.8

    A post-auth SQL injection vulnerability in the Trend Micro Endpoint Encryption PolicyServer could allow an attacker to …

  • High 7.8

    IBM CICS TX code execution

    IBM CICS TX Standard 11.1 and IBM CICS TX Advanced 10.1 and 11.1 could allow a local user to execute arbitrary code on the system due to the use of unsafe use of the gets function.

  • Critical 9.8

    Ruijie Reyee OS Use of Inherently Dangerous Function

    Ruijie Reyee OS versions 2.206.x up to but not including 2.320.x uses an inherently dangerous function which could allow an attacker to send a malicious MQTT message resulting in devices executing arbitrary OS commands.

  • High 7.4

    ColdFusion Use of Inherently Dangerous Function Leads To Security feature bypass  

    ColdFusion version 2021 update 1 (and earlier) and versions 2018.10 (and earlier) are impacted by an Use of Inherently Dangerous Function vulnerability that can lead to a security feature bypass  . An authenticated attacker could leverage this vulnerability t…

  • Unscored —

    Airspan AirVelocity 1500 software prior to version 15.18.00.2511 had NET-SNMP-EXTEND-MIB enabled on its snmpd service, …

  • High 7.8

    AzeoTech DAQFactory

    The affected application uses specific functions that could be abused through a crafted project file, which could lead to code execution, system reboot, and system shutdown.

  • Critical 9.8

    modulemd uses an unsafe function for processing externally provided data

    modulemd 1.3.1 and earlier uses an unsafe function for processing externally provided data, leading to remote code execution.

  • Medium —

    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…