Skip to content
OpenAdvisories

Weakness (CWE)

CWE-732: Incorrect Permission Assignment for Critical Resource

Class Draft

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

How to prevent it (8 mitigations)
  1. 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.

  2. 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]

  3. 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.

  4. 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.

  5. System Configuration

    For all configuration files, executables, and libraries, make sure that they are only readable and writable by the software's administrator.

  6. 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.

  7. Installation

    Do not assume that a system administrator will manually change the configuration to the settings that are recommended in the software's manual.

  8. 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.

Source: MITRE CWE-732

989 results · Feed

  • High 8.1
    CVE-2020-17533 Public exploit

    Apache Accumulo Improper Handling of Insufficient Permissions

    Apache Accumulo versions 1.5.0 through 1.10.0 and version 2.0.0 do not properly check the return value of some policy enforcement functions before permitting an authenticated user to perform certain administrative operations. Specifically, the return values o…

  • Unscored —

    Incorrect permissions are set by default for an API entry-point of a specific service, allowing a non-authenticated use…

  • Low 3.3

    Temp directory permission issue in Guava

    A temp directory creation vulnerability exists in all versions of Guava, allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava API com.google.common.io.Files.createTempDir(). By default, on un…

  • Medium 6.5

    Incorrect Permission Assignment for Critical Resource

    Incorrect Permission Assignment for Critical Resource vulnerability in McAfee VirusScan Enterprise (VSE) prior to 8.8 Patch 16 allows local administrators to bypass local security protection through VSE not correctly integrating with Windows Defender Applicat…

  • Medium 4.3

    Incorrect permission enforcement in UmbracoCms

    Editors/LogViewerController.cs in Umbraco through 8.9.1 allows a user to visit a logviewer endpoint even if they lack Applications.Settings access.

  • Unscored —

    An information-disclosure flaw was found in the way that gluster-block before 0.5.1 logs the output from gluster-block …

  • Medium 6.5

    Privilege Escalation in HashiCorp Consul

    HashiCorp Consul and Consul Enterprise 1.2.0 up to 1.8.5 allowed operators with operator:read ACL permissions to read the Connect CA private key configuration. Fixed in 1.6.10, 1.7.10, and 1.8.6.

  • Medium 5.5

    SaltStack Salt Allows creating certificates with weak file permissions

    The TLS module within SaltStack Salt through 3002 creates certificates with weak file permissions.

  • Critical 9.3

    Libvirt Service Arbitrary File Write Privilege Escalation Vulnerability

    Ubuntu's packaging of libvirt in 20.04 LTS created a control socket with world read and write permissions. An attacker could use this to overwrite arbitrary files or execute arbitrary code.

  • High 7.8

    Acronis True Image 2021 fails to properly set ACLs of the C:\ProgramData\Acronis directory. Because some privileged pro…

  • High 7.8

    This vulnerability allows local attackers to escalate privileges on affected installations of Foxit PhantomPDF 10.0.0.3…

  • High 7.8

    This vulnerability allows local attackers to escalate privileges on affected installations of Foxit Reader 10.0.0.35798…

  • Medium 4.4

    Information disclosure in JUnit4

    In JUnit4 from version 4.7 and before 4.13.1, the test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files a…

  • Unscored —

    WebAccess Node (All versions prior to 9.0.1) has incorrect permissions set for resources used by specific services, whi…

  • Medium 4.9

    Incorrect Permission Assignment for Critical Resource and Permissive List of Allowed Inputs in Keycloak

    A flaw was found in all versions of Keycloak before 10.0.0, where the NodeJS adapter did not support the verify-token-audience. This flaw results in some users having access to sensitive information outside of their permissions.

  • High 8.8

    Insecure permissions on build temporary rootfs in Singularity

    Sylabs Singularity through 3.6.2 has Insecure Permissions on temporary directories used in explicit and implicit container build operations, a different vulnerability than CVE-2020-25039.

  • High 8.1

    Insecure permissions on user namespace / fakeroot temporary rootfs in Singularity

    Sylabs Singularity 3.2.0 through 3.6.2 has Insecure Permissions on temporary directories used in fakeroot or user namespace container execution.

  • Medium 5.5

    A flaw was found in the Linux Kernel before 5.8-rc6 in the ZRAM kernel module, where a user with a local account and th…

  • High 8.2

    Privilege Escalation vulnerability in McAfee DXL for Mac

    Privilege Escalation Vulnerability in the installer in McAfee Data Exchange Layer (DXL) Client for Mac shipped with McAfee Agent (MA) for Mac prior to MA 5.6.6 allows local users to run commands as root via incorrectly applied permissions on temporary files.

  • High 8.8

    Dell EMC Isilon OneFS versions 8.2.2 and earlier and Dell EMC PowerScale OneFS version 9.0.0 contain a privilege escala…

  • Medium 6.5

    This vulnerability allows local attackers to disclose sensitive information on affected installations of Parallels Desk…

  • High 8.5

    Cloud Controller may allow developers to claim sensitive routes

    Cloud Foundry CAPI (Cloud Controller), versions prior to 1.97.0, when used in a deployment where an app domain is also the system domain (which is true in the default CF Deployment manifest), were vulnerable to developers maliciously or accidentally claiming …

  • Medium 6.7

    Dell Encryption versions prior to 10.8 and Dell Endpoint Security Suite versions prior to 2.8 contain a privilege escal…

  • High 8.0

    Dell EMC Isilon OneFS versions 8.2.2 and earlier and Dell EMC PowerScale version 9.0.0 contain a file permissions vulne…

  • Unscored —

    The Baxter Spectrum WBM (v17, v20D29, v20D30, v20D31, and v22D24) telnet Command-Line Interface, grants access to sensi…

  • Low 2.7

    Mattermost Server allows System Admin to modify LDAP account names and email addresses

    An issue was discovered in Mattermost Server before 3.0.0. It has a superfluous API in which the System Admin can change the account name and e-mail address of an LDAP account.

  • High 8.8

    Mattermost Server does not properly restrict use of slash commands

    An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. It allows a bypass of restrictions on use of slash commands.

  • High 8.1

    Mattermost Server has intermittent Authorization bypass for resource-owners

    An issue was discovered in Mattermost Server before 4.2.0, 4.1.1, and 4.0.5, when used as an OAuth 2.0 service provider. Sometimes. resource-owner authorization is bypassed, allowing account takeover.

  • Medium 5.3

    Mattermost Server allows attackers to log sensitive information via DEBUG REST API logging endpoint

    An issue was discovered in Mattermost Server before 4.2.0, 4.1.1, and 4.0.5. It allows attackers to add DEBUG lines to the logs via a REST API version 3 logging endpoint.

  • Medium 4.3

    Mattermost Server allows users with a session ID to revoke another users' session

    An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. Knowledge of a session ID allows revoking another user's session.

  • Medium 6.7

    Dell Encryption versions prior to 10.7 and Dell Endpoint Security Suite versions prior to 2.7 contain a privilege escal…

  • Medium 5.3

    Incorrect Permission Assignment for Critical Resource in Hashicorp Consul

    HashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to non-propagation to secondary data centers. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.

  • Medium 5.5

    Grafana information disclosure

    An information-disclosure flaw was found in Grafana through 6.7.3. The database directory /var/lib/grafana and database file /var/lib/grafana/grafana.db are world readable. This can result in exposure of sensitive information (e.g., cleartext or encrypted dat…

  • Medium 5.5

    Grafana world readable configuration files

    In certain Red Hat packages for Grafana 6.x through 6.3.6, the configuration files /etc/grafana/grafana.ini and /etc/grafana/ldap.toml (which contain a secret_key and a bind_password) are world readable.

  • High 7.3

    ABB System 800xA Weak File Permissions - ABB System 800xA Base

    Insufficient folder permissions used by system functions in ABB System 800xA Base (version 6.1 and earlier) allow low privileged users to read, modify, add and delete system and application files. An authenticated attacker who successfully exploit the vulnera…

  • Medium 5.5

    ABB System 800xA Weak File Permissions - different products

    Insufficient folder permissions used by system functions in ABB System 800xA products OPCServer for AC800M (versions 6.0 and earlier) and Control Builder M Professional, MMSServer for AC800M, Base Software for SoftControl (version 6.1 and earlier) allow low p…

  • High 7.8

    A flaw was found in Linux, in targetcli-fb versions 2.1.50 and 2.1.51 where the socket used by targetclid was world-wri…

  • Unscored —

    In Rockwell Automation RSLinx Classic versions 4.11.00 and prior, an authenticated local attacker could modify a regist…

  • Medium 5.3
    CVE-2020-10883 Public exploit

    This vulnerability allows local attackers to escalate privileges on affected installations of TP-Link Archer A7 Firmwar…

  • High 7.0

    A vulnerability was found in all openshift/mediawiki 4.x.x versions prior to 4.3.0, where an insecure modification vuln…