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

Goal: 1000 CNY · Raised: 1310 CNY

100%
Buy Us a Coffee

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

462 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-2016-2121 Redis Labs Redis 权限许可和访问控制问题漏洞 — redis 5.5 -2018-10-31
CVE-2018-17892 NUUO CMS 安全漏洞 — NUUO CMS 8.8 -2018-10-12
CVE-2018-14650 sos-collector 安全漏洞 — sos-collector 5.0 -2018-09-27
CVE-2016-8637 Dracut 信息泄露漏洞 — dracut 7.8 -2018-08-01
CVE-2017-2590 Red Hat FreeIPA 安全漏洞 — ipa 8.1 -2018-07-27
CVE-2017-12167 Red Hat JBoss Enterprise Application Platform 信息泄露漏洞 — EAP-7 3.3 -2018-07-26
CVE-2016-9604 Linux kernel 安全漏洞 — security 4.4 -2018-07-11
CVE-2012-0433 insecure permissions on files containing confidential data — crowbar 5.5 -2018-06-08
CVE-2018-1115 PostgreSQL adminpack扩展配置错误漏洞 — postgresql 8.2 -2018-05-10
CVE-2017-12713 Advantech WebAccess 安全漏洞 — Advantech WebAccess 7.8 -2017-08-30
CVE-2017-8449 Elastic X-Pack Security 信息泄露漏洞 — Elastic X-Pack Security 6.5 -2017-06-16
CVE-2017-8450 Elastic X-Pack 信息泄露漏洞 — Elastic X-Pack Security 7.5 -2017-06-16

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