CWE-267: Privilege Defined With Unsafe Actions

Code Examples & CVEs

Demonstrative Examples

This code intends to allow only Administrators to print debug information about a system.

While the intention was to only allow Administrators to print the debug information, the code as written only excludes those with the role of "GUEST". Someone with the role of "ADMIN" or "USER" will be allowed access, which goes against the original intent. An attacker may be able to use this debug information to craft an attack on the system.

BadJava

public enum Roles {ADMIN,USER,GUEST}                      public void printDebugInfo(User requestingUser){                         if(isAuthenticated(requestingUser)){                               switch(requestingUser.role){                                     case GUEST:System.out.println("You are not authorized to perform this command");break;                                        default:System.out.println(currentDebugState());break;                                                                       }                            }else{System.out.println("You must be logged in to perform this command");}                      }

Observed CVE Examples (17)

CVE-2002-1981

Roles have access to dangerous procedures (Accessible entities).

View Details

CVE-2002-1671

Untrusted object/method gets access to clipboard (Accessible entities).

View Details

CVE-2004-2204

Gain privileges using functions/tags that should be restricted (Accessible entities).

View Details

CVE-2000-0315

Traceroute program allows unprivileged users to modify source address of packet (Accessible entities).

View Details

CVE-2004-0380

Bypass domain restrictions using a particular file that references unsafe URI schemes (Accessible entities).

View Details

CVE-2002-1154

Script does not restrict access to an update command, leading to resultant disk consumption and filled error logs (Accessible entities).

View Details

CVE-2002-1145

"public" database user can use stored procedure to modify data controlled by the database owner (Unsafe privileged actions).

View Details

CVE-2000-0506

User with capability can prevent setuid program from dropping privileges (Unsafe privileged actions).

View Details

CVE-2002-2042

Allows attachment to and modification of privileged processes (Unsafe privileged actions).

View Details

CVE-2000-1212

User with privilege can edit raw underlying object using unprotected method (Unsafe privileged actions).

View Details

CVE-2005-1742

Inappropriate actions allowed by a particular role(Unsafe privileged actions).

View Details

CVE-2001-1480

Untrusted entity allowed to access the system clipboard (Unsafe privileged actions).

View Details

CVE-2001-1551

Extra Linux capability allows bypass of system-specified restriction (Unsafe privileged actions).

View Details

CVE-2001-1166

User with debugging rights can read entire process (Unsafe privileged actions).

View Details

CVE-2005-1816

Non-root admins can add themselves or others to the root admin group (Unsafe privileged actions).

View Details

CVE-2005-2173

Users can change certain properties of objects to perform otherwise unauthorized actions (Unsafe privileged actions).

View Details

CVE-2005-2027

Certain debugging commands not restricted to just the administrator, allowing registry modification and infoleak (Unsafe privileged actions).

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-267 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-267, Privilege Defined With Unsafe Actions, 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 Environment Hardening controls for Privilege Defined With Unsafe Actions

MITRE associates mitigation with Architecture and Design, and Operation; the listed strategies include Environment Hardening; recorded impacts include Gain Privileges or Assume Identity. Use these source-defined anchors to turn CWE-267 into implementation, review, and verification checks for the affected component.

CWE-267: Privilege Defined With Unsafe Actions — MITRE CWE

Triage CWE-267 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-267, Privilege Defined With Unsafe Actions, 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-267

Apply MITRE's full root-cause mapping guidance when using CWE-267, Privilege Defined With Unsafe Actions. 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-267 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-267, Privilege Defined With Unsafe Actions. 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-267: Privilege Defined With Unsafe Actions?+

CWE-267: Privilege Defined With Unsafe Actions is a Common Weakness Enumeration (CWE) entry maintained by MITRE. A particular privilege, role, capability, or right can be used to perform unsafe actions that were not intended, even when it is assigned to the correct entity.

What are the security consequences of Privilege Defined With Unsafe Actions?+

If exploited, CWE-267 (Privilege Defined With Unsafe Actions) it can compromise Access Control, leading to outcomes such as Gain Privileges or Assume Identity.

Which programming languages are affected by Privilege Defined With Unsafe Actions?+

CWE-267 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 Privilege Defined With Unsafe Actions?+

MITRE documents real CVEs mapped to CWE-267, including CVE-2002-1981, CVE-2002-1671, CVE-2004-2204, CVE-2000-0315 and CVE-2004-0380. 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-267 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-267: Privilege Defined With Unsafe Actions

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Detection Methods

Code Examples & CVEs

Demonstrative Examples

Observed CVE Examples (17)

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-267 with SSDF evidence

Apply Environment Hardening controls for Privilege Defined With Unsafe Actions

Triage CWE-267 against known exploitation evidence

Apply precise root-cause mapping to CWE-267

Validate CWE-267 with root-cause mapping checks

Frequently Asked Questions

Learn More