CWE WEAKNESSES  /  CWE-732

CWE-732

Incorrect Permission Assignment for Critical Resource

What it is

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

When a resource is given a permission setting that provides access to a wider range of actors than required, it could lead to the exposure of sensitive information, or the modification of that resource by unintended parties. This is especially dangerous when the resource is related to program configuration, execution, or sensitive user data. For example, consider a misconfigured storage account for the cloud that can be read or written by a public or anonymous user.

Impact

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. Fo
• [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.

Real-world CVE examples

• 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 wi
• 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
• 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
• 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.

Related weaknesses

Source: MITRE CWE. View on cwe.mitre.org →