CWE-277: Insecure Inherited Permissions
Variant
A product defines a set of insecure permissions that are inherited by objects that are created by the program.
Consequences
- Confidentiality, Integrity: Read Application Data, Modify Application Data
How to prevent it
- Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design: 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.
Recent advisories
- GHSA-7f3r-gwc9-2995 — view_component: Preview Route Can Dispatch Inherited Helper Methods
- GHSA-q3jj-46pq-826r — OpenClaw's ACP child sessions inherit subagent security envelope constraints
- GHSA-j6xf-jwrj-v5qp — Coder vulnerable to privilege escalation could lead to a cross workspace compromise
- GHSA-g5hv-r743-v8pm — Apache Airflow has DAG Author Code Execution possibility in airflow-scheduler
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor