CWE-279: Incorrect Execution-Assigned Permissions

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-279 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-279, Incorrect Execution-Assigned Permissions, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Apply Separation of Privilege controls for Incorrect Execution-Assigned Permissions

MITRE associates mitigation with Architecture and Design, and Operation; the listed strategies include Separation of Privilege; documented detection approaches include Automated Static Analysis. Use these source-defined anchors to turn CWE-279 into implementation, review, and verification checks for the affected component.

CWE-279: Incorrect Execution-Assigned Permissions — MITRE CWE

Triage CWE-279 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-279, Incorrect Execution-Assigned Permissions, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-279

Apply MITRE's full root-cause mapping guidance when using CWE-279, Incorrect Execution-Assigned Permissions. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-279 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-279, Incorrect Execution-Assigned Permissions. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-279: Incorrect Execution-Assigned Permissions?+

CWE-279: Incorrect Execution-Assigned Permissions is a Common Weakness Enumeration (CWE) entry maintained by MITRE. While it is executing, the product sets the permissions of an object in a way that violates the intended permissions that have been specified by the user.

What are the security consequences of Incorrect Execution-Assigned Permissions?+

If exploited, CWE-279 (Incorrect Execution-Assigned Permissions) it can compromise Confidentiality and Integrity, leading to outcomes such as Read Application Data and Modify Application Data.

Which programming languages are affected by Incorrect Execution-Assigned Permissions?+

CWE-279 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Incorrect Execution-Assigned Permissions?+

MITRE documents real CVEs mapped to CWE-279, including CVE-2002-0265, CVE-2003-0876 and CVE-2002-1694. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-279 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-279: Incorrect Execution-Assigned Permissions

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Detection Methods

Code Examples & CVEs

Observed CVE Examples (3)

CWE Relationships

Parent Weaknesses