Description
The software assigns an owner to a resource, but the owner is outside of the intended control sphere.
This may allow the resource to be manipulated by actors outside of the intended control sphere.
Modes of Introduction:
– Architecture and Design
Likelihood of Exploit:
Related Weaknesses
Consequences
Confidentiality, Integrity: Read Application Data, Modify Application Data
An attacker could read and modify data for which they do not have permissions to access directly.
Potential Mitigations
Phase: Policy
Effectiveness:
Description:
Periodically review the privileges and their owners.
Phase: Testing
Effectiveness:
Description:
Use automated tools to check for privilege settings.
CVE References
- CVE-2007-5101
- File system sets wrong ownership and group when creating a new file.
- CVE-2007-4238
- OS installs program with bin owner/group, allowing modification.
- CVE-2007-1716
- Manager does not properly restore ownership of a reusable resource when a user logs out, allowing privilege escalation.
- CVE-2005-3148
- Backup software restores symbolic links with incorrect uid/gid.
- CVE-2005-1064
- Product changes the ownership of files that a symlink points to, instead of the symlink itself.
- CVE-2011-1551
- Component assigns ownership of sensitive directory tree to a user account, which can be leveraged to perform privileged operations.
More Stories
The Most Dangerous Vulnerabilities in Apache Tomcat and How to Protect Against Them
Apache Tomcat is an open-source web server and servlet container that is widely used in enterprise environments to run Java...
ZDI-CAN-18333: A Critical Zero-Day Vulnerability in Microsoft Windows
Zero-day vulnerabilities are a serious threat to cybersecurity, as they can be exploited by malicious actors to gain unauthorized access...
CWE-669 – Incorrect Resource Transfer Between Spheres
Description The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere,...
CWE-67 – Improper Handling of Windows Device Names
Description The software constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a...
CWE-670 – Always-Incorrect Control Flow Implementation
Description The code contains a control flow path that does not reflect the algorithm that the path is intended to...
CWE-671 – Lack of Administrator Control over Security
Description The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect...