| Name |
Block Access to Libraries |
|
| Likelyhood of attack |
Typical severity |
| Medium |
Medium |
|
| Summary |
An application typically makes calls to functions that are a part of libraries external to the application. These libraries may be part of the operating system or they may be third party libraries. It is possible that the application does not handle situations properly where access to these libraries has been blocked. Depending on the error handling within the application, blocked access to libraries may leave the system in an insecure state that could be leveraged by an attacker. |
| Prerequisites |
An application requires access to external libraries. An attacker has the privileges to block application access to external libraries. |
| Execution Flow |
| Step |
Phase |
Description |
Techniques |
| 1 |
Explore |
Determine what external libraries the application accesses. |
|
| 2 |
Experiment |
Block access to the external libraries accessed by the application. |
|
| 3 |
Experiment |
Monitor the behavior of the system to see if it goes into an insecure/inconsistent state. |
|
| 4 |
Experiment |
If the system does go into an insecure/inconsistent state, leverage that to obtain information about the system functionality or data, elevate access control, etc. The rest of this attack will depend on the context and the desired goal. |
|
|
| Solutions | Ensure that application handles situations where access to APIs in external libraries is not available securely. If the application cannot continue its execution safely it should fail in a consistent and secure fashion. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-227 |
7PK - API Abuse |
| CWE-589 |
Call to Non-ubiquitous API |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-603 |
An adversary blocks the delivery of an important system resource causing the system to fail or stop working. |
|