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

374 results · Clear filters · Feed

  • Medium 5.5

    iControl REST and tmsh vulnerability

    Incorrect permission assignment vulnerabilities exist in BIG-IP and BIG-IQ TMOS Shell (tmsh) arp and ndp commands, and in BIG-IP iControl REST. These vulnerabilities may allow an authenticated attacker to view adjacent network information.  Note: Software ver…

  • Medium 6.5

    iControl REST and tmsh vulnerability

    Incorrect permission assignment vulnerabilities exist in iControl REST and TMOS shell (tmsh) undisclosed command which may allow an authenticated attacker to view sensitive information.  Note: Software versions which have reached End of Technical Support (EoT…

  • Medium 4.4

    An incorrect permission assignment for critical resource of Ivanti Secure Access Client   before 22.8R6 allows a local …

  • Medium 5.4

    A configuration file on the local file system had improper input validation which could allow code execution and potent…

  • Medium 6.7

    ACAP applications can gain elevated privileges due to improper input validation during the installation process, potent…

  • Medium 6.1

    Summarize Insecure Daemon Configuration File Permissions

    Summarize versions through 0.14.1, fixed in commit 0cfb0fb, creates the daemon configuration directory and file with default filesystem permissions that may be world-readable on Unix-like systems, allowing local attackers to read bearer tokens and API credent…

  • Medium 5.5

    @axonflow/openclaw fix introduces plugin cache and credential-file permission hardening

    ## Summary Two related permission defects in this AxonFlow plugin allowed registration credentials and cache state to be readable by other local users on hosts where the calling user's home directory was at the conventional `0755` mode. ## Affected versions V…

  • Medium 4.8

    Claude SDK for TypeScript has Insecure Default File Permissions in Local Filesystem Memory Tool

    Claude SDK for TypeScript provides access to the Claude API from server-side TypeScript or JavaScript applications. From version 0.79.0 to before version 0.91.1, the BetaLocalFilesystemMemoryTool in the Anthropic TypeScript SDK created memory files and direct…

  • Medium 6.5

    OpenClaw < 2026.4.8 - Workspace-Only Filesystem Policy Bypass via docx upload_file/upload_image

    OpenClaw before 2026.4.8 contains a filesystem policy bypass vulnerability in docx upload processing that allows local file reads outside workspace boundaries. Attackers can exploit upload_file and upload_image endpoints to access files beyond the intended wo…

  • Medium 5.5

    OpenClaw < 2026.3.31 - Arbitrary Host File Read via appendLocalMediaParentRoots Self-Whitelisting

    OpenClaw before 2026.3.31 contains a local roots self-whitelisting vulnerability in appendLocalMediaParentRoots that allows model-initiated arbitrary host file read. Attackers can exploit improper media parent directory validation to exfiltrate credentials an…

  • Medium 6.5

    OpenClaw < 2026.3.31 - Authentication Boundary Bypass via Telegram Legacy allowFrom Migration

    OpenClaw before 2026.3.31 contains an authentication boundary vulnerability where Telegram legacy allowFrom migration incorrectly fans default-account trust into all named accounts. Attackers can exploit this trust propagation to bypass authentication control…

  • Medium 6.2

    Missing large page handling in pmap_pkru_update_range()

    In order to apply a particular protection key to an address range, the kernel must update the corresponding page table entries. The subroutine which handled this failed to take into account the presence of 1GB largepage mappings created using the shm_create_l…

  • Medium 5.7

    Exposed Session Token in canonical-livepatch client snap

    An improper access control vulnerability in the canonical-livepatch snap client prior to version 10.15.0 allows a local unprivileged user to obtain a sensitive, root-level authentication token by sending an unauthenticated request to the livepatchd.sock Unix …

  • Medium 6.8

    Insight Agent Private Key Information Disclosure via Inherited File Permissions

    The installer certificate files in the …/bootstrap/common/ssl folder do not seem to have restricted permissions on Windows systems (users have read and execute access). For the client.key file in particular, this could potentially lead to exploits, as this ex…

  • Medium 6.7

    Local privilege escalation due to insecure folder permissions. The following products are affected: Acronis True Image …

  • Medium 4.8

    Claude SDK for Python: Insecure Default File Permissions in Local Filesystem Memory Tool

    The Claude SDK for Python provides access to the Claude API from Python applications. From version 0.86.0 to before version 0.87.0, the local filesystem memory tool in the Anthropic Python SDK created memory files with mode 0o666, leaving them world-readable …

  • Medium 5.0

    mmctl export download command doesn’t restrict permissions to created file to file owner

    Mattermost versions 11.4.x <= 11.4.0, 11.3.x <= 11.3.1, 11.2.x <= 11.2.3, 10.11.x <= 10.11.11 fail to set permissions on downloaded bulk export which allows other local users on the server to be able to read contents of the bulk export.. Mattermost Advisory I…

  • Medium 5.5

    A permissions issue was addressed with additional restrictions. This issue is fixed in macOS Sequoia 15.7.5, macOS Sono…

  • Medium 4.9

    This issue was addressed through improved state management. This issue is fixed in macOS Sequoia 15.7.5, macOS Sonoma 1…

  • Medium 4.8

    Halloy has insecure file permissions on credential files

    Halloy is an IRC application written in Rust. In versions on \*nix and macOS prior to commit f180e41061db393acf65bc99f5c5e7397586d9cb, halloy creates its config directory and files using default umask permissions, which typically results in `0644` on files an…

  • Medium 4.3

    Apache Airflow: DAG authorization bypass

    Apache Airflow versions 3.1.0 through 3.1.7 /ui/dependencies endpoint returns the full DAG dependency graph without filtering by authorized DAG IDs. This allows an authenticated user with only DAG Dependencies permission to enumerate DAGs they are not authori…

  • Medium 6.5

    Apache Airflow: Wildcard DagVersion Listing Bypasses Per‑DAG RBAC and Leaks Metadata

    Apache Airflow versions 3.0.0 through 3.1.7 FastAPI DagVersion listing API does not apply per-DAG authorization filtering when the request is made with dag_id set to "~" (wildcard for all DAGs). As a result, version metadata of DAGs that the requester is not …

  • Medium 4.9

    Buffalo TeraStation TS5400R Excessive File Permissions Information Disclosure

    Buffalo TeraStation NAS TS5400R firmware version 4.02-0.06 and prior contain an excessive file permissions vulnerability that allows authenticated attackers to read the /etc/shadow file by uploading and executing a PHP file through the webserver. Attackers ca…

  • Medium 6.5

    SiYuan renderSprig: missing admin check allows any user to read full workspace DB

    SiYuan is a personal knowledge management system. Prior to 3.6.1, POST /api/template/renderSprig lacks model.CheckAdminRole, allowing any authenticated user to execute arbitrary SQL queries against the SiYuan workspace database and exfiltrate all note content…

  • Medium 6.8

    An Incorrect Permission Assignment vulnerability exists in the ASUS Business System Control Interface driver. This vuln…

  • Medium 5.8

    Local Privilege Escalation Due to Writable Executable in Privileged Visionline Service Path

    Incorrect Default Permissions, : Execution with Unnecessary Privileges, : Incorrect Permission Assignment for Critical Resource vulnerability in ASSA ABLOY Visionline on Windows allows Configuration/Environment Manipulation.This issue affects Visionline: from…

  • Medium 6.5

    Incorrect Permission Assignment on power analyzer

    An unauthenticated remote attacker who tricks a user to upload a manipulated HTML file can get access to sensitive information on the device. This is a result of incorrect permission assignment for the web server.

  • Medium 5.5

    Sensitive information disclosure due to improper configuration of a headless browser. The following products are affect…

  • Medium 4.4

    Credentials are not deleted from Acronis Agent after plan revocation. The following products are affected: Acronis Cybe…

  • Medium 4.4

    Credentials are not deleted from Acronis Agent after plan revocation. The following products are affected: Acronis Cybe…

  • Medium 6.6

    Improper permission checks in Extension:NSFileRepo

    Files or Directories Accessible to External Parties, Incorrect Permission Assignment for Critical Resource vulnerability in Hallo Welt! GmbH BlueSpice (Extension:NSFileRepo modules) allows Accessing Functionality Not Properly Constrained by ACLs, Bypassing El…

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

    The following vulnerabilities, which may affect IBM Storage Scale when a directory has a specific ACL composition and could lead to improper execute permissions, have been remediated in Storage Scale versions 5.2.3.6 and 6.0.0.2

    IBM Storage Scale IBM S through rage Scale 5.2.3.0 - 5.2.3.5, and IBM S through rage Scale 6.0.0.0 - 6.0.0.1 could allow a local user to unintentionally trigger additional permissions for resources in a way that allows that resource to be executed by unintend…

  • Medium 5.2

    HP System Event Utility – Denial of Service

    HP System Event Utility might allow denial of service with elevated arbitrary file writes. This potential vulnerability was remediated with HP System Event Utility version 3.2.16.

  • Medium 6.8

    Incorrect Permission Assignment for Critical Resource in Owl opds

    Incorrect Permission Assignment for Critical Resource in Owl opds 2.2.0.4 allows File Manipulation via a crafted network request.

  • Medium 6.5

    Insecure file permissions in Enforce Recovery Key Portal

    Tanium addressed an insecure file permissions vulnerability in Enforce Recovery Key Portal.

  • Medium 6.7

    Incorrect permission assignment for critical resource for some System Firmware Update Utility (SysFwUpdt) for Intel(R) …

  • Medium 6.7

    Docker Desktop for Windows Incorrect Permission Assignment Privilege Escalation Vulnerabilities

    Docker Desktop for Windows contains multiple incorrect permission assignment vulnerabilities in the installer's handling of the C:\ProgramData\DockerDesktop directory. The installer creates this directory without proper ownership verification, creating two ex…

  • Medium 5.5

    HCL AION is susceptible to Incorrect Permission Assignment for Critical Resource

    Root File System Not Mounted as Read-Only configuration vulnerability. This can allow unintended modifications to critical system files, potentially increasing the risk of system compromise or unauthorized changes.This issue affects AION: 2.0.

  • Medium 6.7

    pnpm has Path Traversal via arbitrary file permission modification

    pnpm is a package manager. Prior to version 10.28.2, when pnpm processes a package's `directories.bin` field, it uses `path.join()` without validating the result stays within the package root. A malicious npm package can specify `"directories": {"bin": "../..…