| Name |
Using Malicious Files |
|
| Likelyhood of attack |
Typical severity |
| High |
Very High |
|
| Summary |
An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface. |
| Prerequisites |
System's configuration must allow an attacker to directly access executable files or upload files to execute. This means that any access control system that is supposed to mediate communications between the subject and the object is set incorrectly or assumes a benign environment. |
| Solutions | Design: Enforce principle of least privilege Design: Run server interfaces with a non-root account and/or utilize chroot jails or other configuration techniques to constrain privileges even if attacker gains some limited access to commands. Implementation: Perform testing such as pen-testing and vulnerability scanning to identify directories, programs, and interfaces that grant direct access to executables. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-59 |
Improper Link Resolution Before File Access ('Link Following') |
| CWE-264 |
Permissions, Privileges, and Access Controls |
| CWE-270 |
Privilege Context Switching Error |
| CWE-272 |
Least Privilege Violation |
| CWE-275 |
Permission Issues |
| CWE-282 |
Improper Ownership Management |
| CWE-285 |
Improper Authorization |
| CWE-693 |
Protection Mechanism Failure |
| CWE-732 |
Incorrect Permission Assignment for Critical Resource |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-122 |
An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources. If access control mechanisms are absent or misconfigured, a user may be able to access resources that are intended only for higher level users. An adversary may be able to exploit this to utilize a less trusted account to gain information and perform activities reserved for more trusted accounts. This attack differs from privilege escalation and other privilege stealing attacks in that the adversary never actually escalates their privileges but instead is able to use a lesser degree of privilege to access resources that should be (but are not) reserved for higher privilege accounts. Likewise, the adversary does not exploit trust or subvert systems - all control functionality is working as configured but the configuration does not adequately protect sensitive resources at an appropriate level. |
| CAPEC-233 |
An adversary exploits a weakness enabling them to elevate their privilege and perform an action that they are not supposed to be authorized to perform. |
|
| Taxonomy: ATTACK |
|
Entry ID
|
Entry Name
|
| 1574.010 |
Hijack Execution Flow:Services File Permissions Weakness |
|