#SecurityExplained S-88: CWE Top 25: CWE-732: Incorrect Permission Assignment for Critical Resource
The product defines permissions for a security-critical resource so that unwanted actors can read or modify it.
1/n
The product defines permissions for a security-critical resource so that unwanted actors can read or modify it.
1/n
2/n
When a resource's permissions are set to allow access to a broader range of actors than is required, sensitive information may be exposed, or undesired parties may modify the resource.
When a resource's permissions are set to allow access to a broader range of actors than is required, sensitive information may be exposed, or undesired parties may modify the resource.
3/n
This is very risky when the resource is tied to program configuration, execution, or sensitive user data.
This is very risky when the resource is tied to program configuration, execution, or sensitive user data.
4/n
This flaw arises due to the deployment of an architectural security strategy. The developer may make assumptions about the product's operating environment, such as that the software runs on a single-user system or is only available to trusted administrators.
This flaw arises due to the deployment of an architectural security strategy. The developer may make assumptions about the product's operating environment, such as that the software runs on a single-user system or is only available to trusted administrators.
5/n
Permissions become a concern when the software is run in a different environment.
Permissions become a concern when the software is run in a different environment.
6/n
When the user starts the program, the developer may establish loose permissions to reduce difficulties, then add documentation saying that permissions should be tightened.
When the user starts the program, the developer may establish loose permissions to reduce difficulties, then add documentation saying that permissions should be tightened.
7/n
However, because system administrators and users do not always read the documentation, insecure permissions may be kept unaltered.
However, because system administrators and users do not always read the documentation, insecure permissions may be kept unaltered.
8/n
# Example:
This code creates a new user's home directory and makes that user directory's owner. If the user does not have permission to own the new directory, the directory is removed.
Example Language: PHP
# Example:
This code creates a new user's home directory and makes that user directory's owner. If the user does not have permission to own the new directory, the directory is removed.
Example Language: PHP
9/n
The directory is created with the default permissions 0777 because the optional "mode" argument is absent from the call to mkdir(). Setting the new user as the directory's administrator does not modify the directory's permissions, which are still set to the default.
The directory is created with the default permissions 0777 because the optional "mode" argument is absent from the call to mkdir(). Setting the new user as the directory's administrator does not modify the directory's permissions, which are still set to the default.
10/n
Any user can read and write to the directory by default, allowing an exploit on the user's files.
Any user can read and write to the directory by default, allowing an exploit on the user's files.
11/n
# Potential Impact:
An attacker may be able to delete or damage essential data in the related resource, such as entries from a database, by destroying or corrupting it.
# Potential Impact:
An attacker may be able to delete or damage essential data in the related resource, such as entries from a database, by destroying or corrupting it.
12/n
An attacker could exploit this vulnerability to read private information from the connected resource, such as credentials or configuration information stored in a file.
An attacker could exploit this vulnerability to read private information from the connected resource, such as credentials or configuration information stored in a file.
13/n
To obtain privileges, an attacker may change crucial attributes of the related resource, such as replacing a world-writable executable with Malware.
To obtain privileges, an attacker may change crucial attributes of the related resource, such as replacing a world-writable executable with Malware.
14/n
# Mitigations:
Verify whether a critical resource, such as a configuration file, has insecure permissions (such as being editable by any regular user) & generate an error or even quits the software if there is a chance an unauthorized person has updated the resource.
# Mitigations:
Verify whether a critical resource, such as a configuration file, has insecure permissions (such as being editable by any regular user) & generate an error or even quits the software if there is a chance an unauthorized person has updated the resource.
n/n
Run the code in a "jail" or similar sandbox environment where strict limits separate the process and the operating system.
Run the code in a "jail" or similar sandbox environment where strict limits separate the process and the operating system.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
