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

594 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)

Confidentiality Read 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 Control Gain 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, Other Modify 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)

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.

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]

Effectiveness: Moderate

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

Effectiveness: Limited

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.

Effectiveness: High

System Configuration For 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 ID	Title	CVSS	Severity	Published
CVE-2020-27836	Red Hat OpenShift cluster-ingress-operator 安全漏洞 — cluster-ingress-operator	9.8	-	2022-08-22
CVE-2022-1655	OpenStack 安全漏洞 — OpenStack	6.5	-	2022-07-22
CVE-2022-34891	Corel Parallels Desktop 安全漏洞 — Desktop	7.8	-	2022-07-15
CVE-2022-33695	SAMSUNG Mobile devices InputManagerService 安全漏洞 — Samsung Mobile Devices	5.1	Medium	2022-07-11
CVE-2014-0068	Red Hat openshift node-utils 安全漏洞 — openshift node-util	5.5	-	2022-06-30
CVE-2022-1596	ABB Relion REX640 Insufficient file access control — REX640 PCL1	6.5	Medium	2022-06-21
CVE-2022-31465	Siemens Xpedition Designer 安全漏洞 — Xpedition Designer VX.2.10	7.8	High	2022-06-14
CVE-2022-1348	logrotate 安全漏洞 — logrotate	6.5	-	2022-05-25
CVE-2022-29263	F5 BIG-IP APM 安全漏洞 — BIG-IP APM	7.8	High	2022-05-05
CVE-2022-26340	F5 BIG-IP多款产品安全漏洞 — BIG-IP	4.9	Medium	2022-05-05
CVE-2022-22521	Privilege Escalation in Miele Benchmark Programming Tool — Benchmark Programming Tool	7.3	High	2022-04-27
CVE-2021-23055	F5 NGINX Ingress Controller 安全漏洞 — NGINX Ingress Controller	6.5	-	2022-04-21
CVE-2022-24872	Improper Access Control in shopware — platform	8.1	High	2022-04-20
CVE-2021-38483	ICSA-22-109-03 FANUC ROBOGUIDE Simulation Platform — ROBOGUIDE	6.0	Medium	2022-04-20
CVE-2022-23448	Siemens SIMATIC安全漏洞 — SIMATIC Energy Manager Basic	7.8	-	2022-04-12
CVE-2022-1316	Incorrect Permission Assignment for Critical Resource in zerotier/zerotierone — zerotier/zerotierone	8.8	High	2022-04-11
CVE-2021-36290	Dell Vnx2 Oe For File 安全漏洞 — VNX2	6.4	Medium	2022-04-08
CVE-2022-22516	CODESYS driver SysDrv3S allows SYSTEM users on Microsoft Windows to read and write in restricted memory space. — CODESYS Control RTE (SL)	7.8	High	2022-04-07
CVE-2022-24769	Default inheritable capabilities for linux container should be empty — moby	5.9	Medium	2022-03-24
CVE-2022-21946	suddoers configuration for cscreen not restrictive enough — Factory	5.3	Medium	2022-03-16
CVE-2022-22148	Yokogawa Exaopc 操作系统命令注入漏洞 — CENTUM CS 3000	7.8	-	2022-03-11
CVE-2022-22141	Yokogawa Exaopc 权限许可和访问控制问题漏洞 — CENTUM CS 3000	7.8	-	2022-03-11
CVE-2022-21819	Jetson Linux安全漏洞 — Jetson Nano, Jetson Nano 2GB	7.6	High	2022-03-11
CVE-2021-4199	Incorrect Permission Assignment for Critical Resource vulnerability in BDReinit.exe (VA-10017) — Total Security	7.8	High	2022-03-07
CVE-2021-3631	Red Hat libvirt 安全漏洞 — libvirt	6.3	-	2022-03-02
CVE-2022-0247	Write access to VMO data through copy-on-write in Fuchsia — Fuchsia	7.5	High	2022-02-25
CVE-2021-3557	Red Hat OpenShift GitOps 授权问题漏洞 — argocd	6.5	-	2022-02-16
CVE-2022-0532	CRI-O 安全漏洞 — cri-o	4.2	-	2022-02-09
CVE-2021-22284	SECURITY - OPC Server for AC 800M - Remote Code Execution Vulnerability — 800xA, Control Software for AC 800M OPC Server for AC 800M	8.4	High	2022-02-04
CVE-2022-0277	Incorrect Permission Assignment for Critical Resource in microweber/microweber — microweber/microweber	-	-	2022-01-20

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