CWE-732: Incorrect Permission Assignment for Critical Resource
1592 CVEs have CWE-732 as their primary weakness. 4 of them are in the CISA KEV catalog. The highest EPSS score among them is 89.132%.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Child of CWE-285: Improper Authorization
Mitigations
- Implementation: When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user) [REF-62], and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Architecture and Design: Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources. [REF-207]
- Architecture and Design Operation: Run the code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software. OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Implementation Installation: During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
- System Configuration: For all configuration files, executables, and libraries, make sure that they are only readable and writable by the software's administrator.
- Documentation: Do not suggest insecure configuration changes in documentation, especially if those configurations can extend to resources and other programs that are outside the scope of the application.
- Installation: Do not assume that a system administrator will manually change the configuration to the settings that are recommended in the software's manual.
- Operation System Configuration: Ensure that the software runs properly under the United States Government Configuration Baseline (USGCB) [REF-199] or an equivalent hardening configuration guide, which many organizations use to limit the attack surface and potential risk of deployed software.
- Implementation System Configuration Operation: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.
Observed examples
- CVE-2026-53657: helper agent in a Linux VM launcher creates a root-owned Unix domain socket with world-writable permissions, allowing code execution from VM guests
- CVE-2022-29527: Go application for cloud management creates a world-writable sudoers file that allows local attackers to inject sudo rules and escalate privileges to root by winning a race condition.
- CVE-2009-3482: Anti-virus product sets insecure Everyone: Full Control permissions for files under the Program Files folder, allowing attackers to replace executables with Trojan horses.
- CVE-2009-3897: Product creates directories with 0777 permissions at installation, allowing users to gain privileges and access a socket used for authentication.
- CVE-2009-3489: Photo editor installs a service with an insecure security descriptor, allowing users to stop or start the service, or execute commands as SYSTEM.
- CVE-2020-15708: socket created with insecure permissions
- CVE-2009-3289: Library function copies a file to a new target and uses the source file's permissions for the target, which is incorrect when the source file is a symbolic link, which typically has 0777 permissions.
- CVE-2009-0115: Device driver uses world-writable permissions for a socket file, allowing attackers to inject arbitrary commands.
- CVE-2009-1073: LDAP server stores a cleartext password in a world-readable file.
- CVE-2009-0141: Terminal emulator creates TTY devices with world-writable permissions, allowing an attacker to write to the terminals of other users.
- CVE-2008-0662: VPN product stores user credentials in a registry key with Everyone: Full Control permissions, allowing attackers to steal the credentials.
- CVE-2008-0322: Driver installs its device interface with Everyone: Write permissions.
- CVE-2009-3939: Driver installs a file with world-writable permissions.
- CVE-2009-3611: Product changes permissions to 0777 before deleting a backup; the permissions stay insecure for subsequent backups.
- CVE-2007-6033: Product creates a share with Everyone: Full Control permissions, allowing arbitrary program execution.
- CVE-2007-5544: Product uses Everyone: Full Control permissions for memory-mapped files (shared memory) in inter-process communication, allowing attackers to tamper with a session.
- CVE-2005-4868: Database product uses read/write permissions for everyone for its shared memory, allowing theft of credentials.
- CVE-2004-1714: Security product uses Everyone: Full Control permissions for its configuration files.
- CVE-2001-0006: Everyone: Full Control permissions assigned to a mutex allows users to disable network connectivity.
- CVE-2002-0969: Chain: database product contains buffer overflow that is only reachable through a .ini configuration file - which has Everyone: Full Control permissions.
Top released CVEs
KEV first, then the highest EPSS score, the highest CVSS score and the newest.
| CVE | Published | Severity | CVSS | EPSS | Description |
|---|---|---|---|---|---|
| CVE-2019-15752 | 2019-08-28 | HIGH | 7.8 | 48.782% | Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-credential-wincred.exe file in… |
| CVE-2018-13374 | 2019-01-22 | MEDIUM | 4.3 | 38.088% | A Improper Access Control in Fortinet FortiOS 6.0.2, 5.6.7 and before, FortiADC 6.1.0, 6.0.0 to 6.0.1, 5.4.0 to 5.4.4 allows attacker to obtain the LDAP server… |
| CVE-2022-22960 | 2022-04-13 | HIGH | 7.8 | 35.519% | VMware Workspace ONE Access, Identity Manager and vRealize Automation contain a privilege escalation vulnerability due to improper permissions in support… |
| CVE-2026-123039 | 2026-11-12 | HIGH | 7.8 | 1.938% | The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket (/tmp/dynamic_socket) without authenticating connecting processes. An… |
| CVE-2026-129950 | 2026-11-16 | MEDIUM | 6.3 | 0.286% | Rowy through 3.0.0 contains an incorrect permission assignment vulnerability in default Firebase Storage rules that grants any user holding a role read and… |
| CVE-2025-5809 | 2026-11-16 | HIGH | 7.1 | 0.269% | An improper privilege management vulnerability in an LDAP extension used with OpenText eDirectory could require a technical or proxy user to be granted write… |
| CVE-2026-21175 | 2026-11-16 | HIGH | 8.6 | 0.151% | Incorrect permission assignment for critical resource in Samsung Update prior to version 3.0.111.0 allows local attackers to execute arbitrary code. |
| CVE-2026-130327 | 2026-11-16 | CRITICAL | 9.3 | 0.125% | In Open Object Rexx (ooRexx) before 5.2.0, RXAPI relies on a world-writable /tmp file unless XDG_RUNTIME_DIR is set, or localhost TCP port 10010, allowing… |
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-732'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-732'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).