Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1020 CNY

100%
Buy Us a Coffee

CWE-732 (关键资源的不正确权限授予) — Vulnerability Class 460

460 vulnerabilities classified as CWE-732 (关键资源的不正确权限授予). AI Chinese analysis included.

CWE-732 represents a critical access control weakness where software assigns overly permissive security attributes to vital resources, such as files, directories, or registry keys. This misconfiguration allows unintended actors to read or modify data that should remain restricted, often leading to sensitive information disclosure or unauthorized system changes. Attackers typically exploit this by identifying these loose permissions to access confidential data or alter critical configurations, potentially escalating privileges or compromising system integrity. To prevent this, developers must adhere to the principle of least privilege, ensuring resources are accessible only to necessary processes and users. Rigorous code reviews, automated static analysis tools, and strict adherence to secure coding standards help identify and correct improper permission assignments before deployment, thereby safeguarding critical assets against unauthorized access and manipulation.

MITRE CWE Description
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.
Common Consequences (3)
ConfidentialityRead Application Data, Read Files or Directories
An attacker may be able to read sensitive information from the associated resource, such as credentials or configuration information stored in a file.
Access ControlGain Privileges or Assume Identity
An attacker may be able to modify critical properties of the associated resource to gain privileges, such as replacing a world-writable executable with a Trojan horse.
Integrity, OtherModify Application Data, Other
An attacker may be able to destroy or corrupt critical data in the associated resource, such as deletion of records from a database.
Mitigations (5)
ImplementationWhen 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 DesignDivide 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]
Effectiveness: Moderate
Architecture and Design, OperationRun 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 ex…
Effectiveness: Limited
Implementation, InstallationDuring 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.
Effectiveness: High
System ConfigurationFor all configuration files, executables, and libraries, make sure that they are only readable and writable by the software's administrator.
Effectiveness: High
Examples (2)
The following code sets the umask of the process to 0 before creating a file and writing "Hello world" into the file.
#define OUTFILE "hello.out" umask(0); FILE *out; /* Ignore link following (CWE-59) for brevity */ out = fopen(OUTFILE, "w"); if (out) { fprintf(out, "hello world!\n"); fclose(out); }
Bad · C
-rw-rw-rw- 1 username 13 Nov 24 17:58 hello.out
Result
This code creates a home directory for a new user, and makes that user the owner of the directory. If the new directory cannot be owned by the user, the directory is deleted.
function createUserDir($username){ $path = '/home/'.$username; if(!mkdir($path)){ return false; } if(!chown($path,$username)){ rmdir($path); return false; } return true; }
Bad · PHP
CVE IDTitleCVSSSeverityPublished
CVE-2025-48382 Fess has Insecure Temporary File Permissions — fess 5.5AIMediumAI2025-05-27
CVE-2025-40672 Privilege Escalation in Panloader.exe — Panloader.exe 7.8AIHighAI2025-05-26
CVE-2025-32915 Sensitive data exposed during automatic agent updates — Checkmk 5.5AIMediumAI2025-05-22
CVE-2025-3944 Incorrect Permission Assignment for Critical Resource — Niagara Framework 7.2 High2025-05-22
CVE-2025-3936 Incorrect Permission Assignment for Critical Resource — Niagara Framework 6.5 Medium2025-05-22
CVE-2025-2759 GStreamer Incorrect Permission Assignment Local Privilege Escalation Vulnerability — GStreamer 7.8AIHighAI2025-05-22
CVE-2025-34025 Versa Concerto Insecure Docker Mount Container Escape — Concerto 9.8AICriticalAI2025-05-21
CVE-2025-40574 Siemens SCALANCE LPE9403 安全漏洞 — SCALANCE LPE9403 7.8 High2025-05-13
CVE-2025-40572 Siemens SCALANCE LPE9403 安全漏洞 — SCALANCE LPE9403 5.5 Medium2025-05-13
CVE-2025-24009 Siemens SIRIUS 3RK3 Modular Safety System和Siemens SIRIUS Safety Relays 3SK2 安全漏洞 — SIRIUS 3RK3 Modular Safety System (MSS) 5.9 Medium2025-05-13
CVE-2025-42997 Information Disclosure vulnerability in SAP Gateway Client — SAP Gateway Client 6.6 Medium2025-05-13
CVE-2025-26168 IXON VPN Client 安全漏洞 — VPN Client 8.1 High2025-05-07
CVE-2025-26169 IXON VPN Client 安全漏洞 — VPN Client 8.1 High2025-05-07
CVE-2025-23245 NVIDIA vGPU 安全漏洞 — vGPU Software, Cloud Gaming 5.5 Medium2025-05-01
CVE-2025-3395 ABB Automation Builder 安全漏洞 — Automation Builder 7.1 High2025-04-30
CVE-2025-3394 Vulnerability in user management of Automation Builder — Automation Builder 7.8 High2025-04-30
CVE-2025-30408 Acronis Cyber Protect Cloud Agent 安全漏洞 — Acronis Cyber Protect Cloud Agent 7.8 -2025-04-24
CVE-2025-0926 AXIS Camera Station Pro 安全漏洞 — AXIS Camera Station Pro 5.9 Medium2025-04-23
CVE-2025-1731 Zyxel USG FLEX 安全漏洞 — USG FLEX H series uOS firmware 7.8 High2025-04-22
CVE-2025-0758 Hitachi Vantara Pentaho Business Analytics Server - Incorrect Permission Assignment for Critical Resource — Pentaho Business Analytics Server 6.1 Medium2025-04-16
CVE-2024-13861 Secureworks Taegis Endpoint Agent 安全漏洞 — Taegis Endpoint Agent (Linux) 7.8 High2025-04-11
CVE-2025-20233 Incorrect permissions set by the “chmod“ and “makedirs“ Python functions in Splunk App for Lookup File Editing — Splunk App for Lookup File Editing 2.5 Low2025-03-26
CVE-2025-2098 Dylib Hijacking in Fast CAD Reader — Fast CAD Reader 7.8AIHighAI2025-03-26
CVE-2024-10209 Incorrect Permission Assignment in APROL file system — APROL 7.1AIHighAI2025-03-25
CVE-2025-27688 Dell ThinOS 安全漏洞 — Wyse Proprietary OS (Modern ThinOS) 7.8 High2025-03-18
CVE-2025-22454 Ivanti Secure Access Client 安全漏洞 — Secure Access Client 7.8 High2025-03-11
CVE-2025-1413 Dylib Hijacking in DaVinci Resolve — DaVinci Resolve 7.8 -2025-02-28
CVE-2025-1067 There is a code injection vulnerability in ArcGIS Pro — ArcGIS Pro 7.3 High2025-02-25
CVE-2025-27141 Metabase Enterprise Edition allows cached questions to leak data to impersonated users — metabase 4.3 -2025-02-24
CVE-2024-13813 Ivanti Secure Access Client 安全漏洞 — Secure Access Client 7.1 High2025-02-11

Vulnerabilities classified as CWE-732 (关键资源的不正确权限授予) represent 460 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.