Exposed Dangerous Method or Function |
Weakness ID: 749 (Weakness Base) | Status: Incomplete |
Description Summary
Extended Description
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:
1) The function/method was never intended to be exposed to outside actors.
2) 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.
Scope | Effect |
---|---|
Integrity | Technical Impact: Gain privileges 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. |
Example 1
In the following Java example the method removeDatabase will delete the database with the name specified in the input parameter.
The method in this example is declared public and therefore is exposed to any class in the application. Deleting a database should be considered a critical operation within an application and access to this potentially dangerous method should be restricted. Within Java this can be accomplished simply by declaring the method private thereby exposing it only to the enclosing class as in the following example.
Reference | Description |
---|---|
CVE-2007-6382 | arbitrary Java code execution via exposed method |
CVE-2007-1112 | security tool ActiveX control allows download or upload of files |
Phase: 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. |
Phases: Architecture and Design; Implementation Strategy: Identify and Reduce Attack Surface 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. |
Ordinality | Description |
---|---|
Primary | (where the weakness exists independent of other weaknesses) |
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 485 | Insufficient Encapsulation | Development Concepts (primary)699 Research Concepts (primary)1000 |
ChildOf | ![]() | 691 | Insufficient Control Flow Management | Research Concepts1000 |
ChildOf | ![]() | 808 | 2010 Top 25 - Weaknesses On the Cusp | Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors (primary)800 |
ParentOf | ![]() | 618 | Exposed Unsafe ActiveX Method | Research Concepts (primary)1000 |
ParentOf | ![]() | 782 | Exposed IOCTL with Insufficient Access Control | Development Concepts (primary)699 Research Concepts (primary)1000 |
Under-reported and under-studied. This weakness could appear in any technology, language, or framework that allows the programmer to provide a functional interface to external parties, but it is not heavily reported. In 2007, CVE began showing a notable increase in reports of exposed method vulnerabilities in ActiveX applications, as well as IOCTL access to OS-level resources. These weaknesses have been documented for Java applications in various secure programming sources, but there are few reports in CVE, which suggests limited awareness in most parts of the vulnerability research community. |
Submissions | ||||
---|---|---|---|---|
Submission Date | Submitter | Organization | Source | |
2008-11-24 | Internal CWE Team | |||
Modifications | ||||
Modification Date | Modifier | Organization | Source | |
2009-01-12 | CWE Content Team | MITRE | Internal | |
updated Name | ||||
2009-07-27 | CWE Content Team | MITRE | Internal | |
updated Relationships | ||||
2009-12-28 | CWE Content Team | MITRE | Internal | |
updated Applicable Platforms, Likelihood of Exploit | ||||
Previous Entry Names | ||||
Change Date | Previous Entry Name | |||
2009-01-12 | Exposed Insecure Method or Function | |||