Insecure Preserved Inherited Permissions

Incomplete Variant
Structure: Simple
Description

This vulnerability occurs when a software product copies or extracts files while unintentionally preserving insecure permissions from their original source, such as an archive, without the user's knowledge or consent.

Extended Description

When a program extracts files from an archive (like a ZIP or TAR file) or copies them from another location, it often replicates the original file permissions or access rights. If those source permissions are overly permissive—for example, allowing any user to read or modify sensitive files—this insecure configuration is silently carried over to the new system. The user or administrator is typically unaware this has happened, creating a hidden security gap where protected data could be exposed or altered. To prevent this, developers should ensure their file operations explicitly set secure, context-appropriate permissions during extraction or copying, rather than blindly inheriting them. This involves stripping or resetting permissions by default and providing clear logging or user prompts when risky permissions are detected. Implementing these safeguards closes the window where an attacker could exploit preserved access rights from a seemingly harmless file transfer.

Common Consequences 1
Scope: ConfidentialityIntegrity

Impact: Read Application DataModify Application Data

Potential Mitigations 2
Phase: Architecture and DesignOperation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Phase: Architecture and Design

Strategy: Separation of Privilege

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.
Observed Examples 1
CVE-2005-1724Does not obey specified permissions when exporting.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Architecture and Design
Operation
Taxonomy Mapping
  • PLOVER