CWE-224: Obscured Security-relevant Information by Alternate Name

Code Examples & CVEs

Demonstrative Examples

This code prints the contents of a file if a user has permission.

While the code logs a bad access attempt, it logs the user supplied name for the file, not the canonicalized file name. An attacker can obscure their target by giving the script the name of a link to the file they are attempting to access. Also note this code contains a race condition between the is_link() and readlink() functions (CWE-363).

BadPHP

function readFile($filename){                         $user = getCurrentUser();$realFile = $filename;                                                        //resolve file if its a symbolic link                            if(is_link($filename)){$realFile = readlink($filename);}                            if(fileowner($realFile) == $user){echo file_get_contents($realFile);return;}else{echo 'Access denied';writeLog($user . ' attempted to access the file '. $filename . ' on '. date('r'));}                      }

Observed CVE Examples (1)

CVE-2002-0725

Attacker performs malicious actions on a hard link to a file, obscuring the real target file.

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-224 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-224, Obscured Security-relevant Information by Alternate Name, 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

Make elimination of CWE-224 a product outcome

Apply CISA's Secure by Design principle of taking ownership of customer security outcomes to CWE-224, Obscured Security-relevant Information by Alternate Name. Put the weakness in the product threat model and security roadmap, fund class-level design and platform changes, prefer safe defaults and reusable guardrails, and publish measurable progress. Do not transfer the primary burden to customer configuration when the manufacturer can remove or contain the root cause in the product.

Shifting the Balance of Cybersecurity Risk: Secure by Design Software — Cybersecurity and Infrastructure Security Agency

Connect Obscured Security-relevant Information by Alternate Name to documented attack evidence

Recorded impacts include Hide Activities, and Gain Privileges or Assume Identity; observed examples include CVE-2002-0725; related weaknesses include CWE-221. Use these source-defined anchors to turn CWE-224 into implementation, review, and verification checks for the affected component.

CWE-224: Obscured Security-relevant Information by Alternate Name — MITRE CWE

Apply precise root-cause mapping to CWE-224

Apply MITRE's full root-cause mapping guidance when using CWE-224, Obscured Security-relevant Information by Alternate Name. 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-224 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-224, Obscured Security-relevant Information by Alternate Name. 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-224: Obscured Security-relevant Information by Alternate Name?+

CWE-224: Obscured Security-relevant Information by Alternate Name is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product records security-relevant information according to an alternate name of the affected entity, instead of the canonical name.

What are the security consequences of Obscured Security-relevant Information by Alternate Name?+

If exploited, CWE-224 (Obscured Security-relevant Information by Alternate Name) it can compromise Non-Repudiation and Access Control, leading to outcomes such as Hide Activities and Gain Privileges or Assume Identity.

Which programming languages are affected by Obscured Security-relevant Information by Alternate Name?+

CWE-224 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 Obscured Security-relevant Information by Alternate Name?+

MITRE documents real CVEs mapped to CWE-224, including CVE-2002-0725. 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-224 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-224: Obscured Security-relevant Information by Alternate Name

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Detection Methods