CWE-749: Exposed Dangerous Method or Function

How it's found

Exposed Dangerous Method or Function is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.

This weakness can lead to a wide variety of resultant weaknesses, depending on the behavior of the exposed method. It can apply to any number of technologies and approaches, such as ActiveX controls, Java functions, IOCTLs, and so on. The exposure can occur in a few different ways:The function/method was never intended to be exposed to outside actors. The function/method was only intended to be accessible to a limited set of actors, such as Internet-based access from a single web site.

Vulnerable vs. safe

Statement stmt = conn.createStatement();stmt.execute("DROP DATABASE " + databaseName);try {} catch (SQLException ex) {...}public void removeDatabase(String databaseName) {}

Statement stmt = conn.createStatement();stmt.execute("DROP DATABASE " + databaseName);
try {} catch (SQLException ex) {...}}private void removeDatabase(String databaseName) {

Consequences

• Gain Privileges or Assume Identity, Read Application Data, Modify Application Data, Execute Unauthorized Code or Commands, Other: Exposing critical functionality essentially provides an attacker with the privilege level of the exposed functionality. This could result in the modification or exposure of sensitive data or possibly even execution of arbitrary code.

Mitigations

• Architecture and Design: If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.
• Architecture and Design/Implementation: Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be: Ensure that the implemented code follows these expectations. This includes setting the appropriate access modifiers where applicable (public, private, protected, etc.) or not marking ActiveX controls safe-for-scripting.accessible to all users restricted to a small set of privileged users prevented from being directly accessible at all

Where this fits in a TurboPentest engagement

This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.

Frequently asked questions

Related CWEs

• Pillar weakness
  CWE-284: Improper Access Control