BaseIncomplete
CWE-272Least Privilege Violation
Category: authz
Description
The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.
Common consequences· 1
- Access Control / Confidentiality — Gain Privileges or Assume Identity, Read Application Data, Read Files or DirectoriesAn attacker may be able to access resources with the elevated privilege that could not be accessed with the attacker's original privileges. This is particularly likely in conjunction with another flaw, such as a buffer overflow.
Potential mitigations· 3
- [Architecture and Design, Operation]Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- [Architecture and Design]Follow the principle of least privilege when assigning access rights to entities in a software system.
- [Architecture and Design]
Related CAPEC attack patterns· 3
References
Exploits (incoming)3
| Type | Target | Confidence | Tier |
|---|---|---|---|
| AttackPattern | Using Malicious Filescapec-17 | 100% | live |
| AttackPattern | Leverage Executable Code in Non-Executable Filescapec-35 | 100% | live |
| AttackPattern | Manipulating Web Input to File System Callscapec-76 | 100% | live |
(incoming)3
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Vulnerability | CVE-2025-47809cve-2025-47809 | 0% | live |
| Vulnerability | CVE-2025-59106cve-2025-59106 | 0% | live |
| Vulnerability | CVE-2025-7722cve-2025-7722 | 0% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.