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

435 results · Clear filters · Feed

  • 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…

  • 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 …

  • 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…

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

  • 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…

  • 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…

  • 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…

  • High 7.0

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

  • High 7.0

    It has been found that in openshift-enterprise version 3.11 and openshift-enterprise versions 4.1 up to, including 4.3,…

  • High 8.8

    keystone_json_assignment backend granted access to any project for users in user-project-map.json

    The keystone-json-assignment package in SUSE Openstack Cloud 8 before commit d7888c75505465490250c00cc0ef4bb1af662f9f every user listed in the /etc/keystone/user-project-map.json was assigned full "member" role access to every project. This allowed these user…

  • High 7.8

    Ruby_parser-legacy Incorrect Permission Assignment for Critical Resource

    The ruby_parser-legacy (aka legacy) gem 1.0.0 for Ruby allows local privilege escalation because of world-writable files. For example, if the brakeman gem (which has a legacy dependency) 4.5.0 through 4.7.0 is used, a local user can insert malicious code into…

  • High 8.1

    Dell EMC Avamar Server versions 7.4.1, 7.5.0, 7.5.1, 18.2 and 19.1 and Dell EMC Integrated Data Protection Appliance (I…

  • High 7.8
    CVE-2019-15752 Exploited Public exploit EPSS 49%

    Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-…

    KEV Nov 3, 2021
  • High 8.8

    A vulnerability was found in libvirt >= 4.1.0 in the virtlockd-admin.socket and virtlogd-admin.socket systemd units. A …

  • High 8.8

    Incorrect Permission Assignment for Critical Resource in Singularity

    An issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious user with local/network access to the host system (e.g. ssh) could exploit this vulnerability due to insecure permissions allowing a user to edit files within `/run/singularity/instances/s…

  • High 8.8

    Paramiko Authentication Bypass vulnerability

    Paramiko version 2.4.1, 2.3.2, 2.2.3, 2.1.5, 2.0.8, 1.18.5, 1.17.6 contains a Incorrect Access Control vulnerability in SSH server that can result in RCE. This attack appear to be exploitable via network connectivity.

  • High 8.1

    A vulnerability was found in ipa before 4.4. IdM's ca-del, ca-disable, and ca-enable commands did not properly check th…

  • High 7.2
    CVE-2018-1000207 EPSS 64%

    MODX Revolution Incorrect Access Control vulnerability

    MODX Revolution version <=2.6.4 contains a Incorrect Access Control vulnerability in Filtering user parameters before passing them into phpthumb class that can result in Creating file with custom a filename and content. This attack appear to be exploitable vi…

  • High 7.5

    Doorkeeper subject to Incorrect Permission Assignment

    Doorkeeper version 4.2.0 and later contains a Incorrect Access Control vulnerability in Token revocation API's authorized method that can result in Access tokens are not revoked for public OAuth apps, leaking access until expiry.

  • High 7.5

    Froxlor Incorrect Access Control

    Froxlor through 0.9.39.5 has Incorrect Access Control for tickets not owned by the current user.

  • High 8.8

    OpenWrt mishandles access control in /etc/config/rpcd and the /usr/share/rpcd/acl.d files, which allows remote authenti…

  • High 7.8

    Incorrect Access Control in Phusion Passenger

    An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the …

  • High 8.8

    express-cart allows any user to create an admin user

    expressCart before 1.1.6 allows remote attackers to create an admin user via a /admin/setup Referer header.

  • High 7.5

    LightSAML Incorrect Access Control vulnerability

    LightSAML version prior to 1.3.5 contains a Incorrect Access Control vulnerability in signature validation in readers in src/LightSaml/Model/XmlDSig/ that can result in impersonation of any user from Identity Provider. This vulnerability appears to have been …

  • High 7.8

    Incorrect Permission Assignment for Critical Resource in NPM

    An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow lo…

  • High 8.8

    PrivateVPN 2.0.31 for macOS suffers from a root privilege escalation vulnerability. The software installs a privileged …

  • High 8.1

    Jerome Gamez Firebase Admin SDK for PHP Incorrect Access Control vulnerability

    Jerome Gamez Firebase Admin SDK for PHP version from 3.2.0 to 3.8.0 contains a Incorrect Access Control vulnerability in src/Firebase/Auth/IdTokenVerifier.php does not verify for token signature that can result in JWT with any email address and user ID could …

  • High 8.8

    Arbitrary code execution vulnerability in Jenkins Speaks! Plugin

    Jenkins Speaks! Plugin, all current versions, allows users with Job/Configure permission to run arbitrary Groovy code inside the Jenkins JVM, effectively elevating privileges to Overall/Run Scripts.

  • High 7.8

    High severity vulnerability that affects org.scala-lang:scala-compiler

    The compilation daemon in Scala before 2.10.7, 2.11.x before 2.11.12, and 2.12.x before 2.12.4 uses weak permissions for private files in /tmp/scala-devel/${USER:shared}/scalac-compile-server-port, which allows local users to write to arbitrary class files an…

  • High 7.8

    Moderate severity vulnerability that affects org.apache.hadoop:hadoop-main

    In Apache Hadoop versions 2.6.1 to 2.6.5, 2.7.0 to 2.7.3, and 3.0.0-alpha1, if a file in an encryption zone with access permissions that make it world readable is localized via YARN's localization mechanism, that file will be stored in a world-readable locati…

  • High 8.8

    Arbitrary code execution due to incomplete sandbox protection in Jenkins Pipeline

    Arbitrary code execution due to incomplete sandbox protection: Constructors, instance variable initializers, and instance initializers in Pipeline scripts were not subject to sandbox protection, and could therefore execute arbitrary code. This could be exploi…

  • High 8.8

    Statamic framework Incorrect Permission Assignment

    Statamic framework before 2.6.0 does not correctly check a session's permissions when the methods from a user's class are called. Problematic methods include reset password, create new account, create new role, etc.

  • High 8.8
    CVE-2017-9462 Public exploit EPSS 22%

    Mercurial has Incorrect Permission Assignment for Critical Resource

    In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and consequently execute arbitrary code, by using --debugger as a repository name.

  • High 7.8

    TrustPort Antivirus before 2.8.0.2266 and PC Security before 2.0.0.1291 use weak permissions (Everyone: Full Control) f…