CWE-278
Insecure Preserved Inherited Permissions
Description
A product inherits a set of insecure permissions for an object, e.g. when copying from an archive file, without user awareness or involvement.
Parent Weaknesses (ChildOf)
Common Consequences
Scope
Impact
Read Application Data, Modify Application Data
Potential Mitigations
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
CVE-2005-1724Does not obey specified permissions when exporting.
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now