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

All Critical High Medium Low Exploited only Public exploit

12 results · Clear filters · Feed

  • Medium 6.2
    CVE-2026-15430 Public exploit

    CVE-2026-15430

    Improper access control in the IRP_MJ_WRITE command interface in Wellbia XIGNCODE3 xhunter2.sys, version 2026.6.1.192, allows a local, unprivileged attacker to achieve local privilege escalation to NT AUTHORITY\SYSTEM, extract credentials from PPL-protected l…

    Wellbia XIGNCODE3
  • Medium 6.6
    CVE-2025-70342 Public exploit

    erase-install prior to v40.4 commit 2c31239 writes swiftDialog credential output to a hardcoded path /var/tmp/dialog.js…

  • Medium 6.8
    CVE-2025-31702 Public exploit

    A vulnerability exists in certain Dahua embedded products. Third-party malicious attacker with obtained normal user cre…

    Dahua IPC SD
  • Medium 6.3
    CVE-2025-49131 Public exploit

    FastGPT Sandbox Vulnerable to Sandbox Bypass

    FastGPT is an open-source project that provides a platform for building, deploying, and operating AI-driven workflows and conversational agents. The Sandbox container (fastgpt-sandbox) is a specialized, isolated environment used by FastGPT to safely execute u…

    labring FastGPT
  • Medium 6.8
    CVE-2025-27591 Public exploit

    Below has Incorrect Permission Assignment for Critical Resource

    A privilege escalation vulnerability existed in the Below service prior to v0.9.0 due to the creation of a world-writable directory at /var/log/below. This could have allowed local unprivileged users to escalate to root privileges through symlink attacks that…

    Meta Platforms below below crates.io
  • Medium 4.7
    CVE-2024-54910 Public exploit

    Hasleo Backup Suite Free v4.9.4 and before is vulnerable to Insecure Permissions via the File recovery function.

  • Medium 6.7
    CVE-2024-28589 Public exploit

    An issue was discovered in Axigen Mail Server for Windows versions 10.5.18 and before, allows local low-privileged atta…

  • Medium 4.4
    CVE-2024-21305 Public exploit

    Hypervisor-Protected Code Integrity (HVCI) Security Feature Bypass Vulnerability

    Hypervisor-Protected Code Integrity (HVCI) Security Feature Bypass Vulnerability

    Microsoft Windows Server 2019 Windows Server 2019 (Server Core installation) Windows 10 Version 1809 Windows
  • Medium 6.5
    CVE-2023-24626 Public exploit

    socket.c in GNU Screen through 4.9.0, when installed setuid or setgid (the default on platforms such as Arch Linux and …

    screen screen screen Debian Ubuntu Alpine
  • Medium 6.3
    CVE-2021-41091 Public exploit

    Insufficiently restricted permissions on data directory in Docker Engine

    Moby is an open-source project created by Docker to enable software containerization. A bug was found in Moby (Docker Engine) where the data directory (typically `/var/lib/docker`) contained subdirectories with insufficiently restricted permissions, allowing …

    moby moby docker.io docker.io Debian Ubuntu Alpine Go
  • 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…

    TP-Link Archer A7 Network devices
  • Medium 4.3
    CVE-2018-13374 Exploited · Ransomware Public exploit EPSS 38%

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

    Fortinet Fortinet FortiOS, fortiADC Network devices
    KEV Sep 8, 2022