CWE-669: Incorrect Resource Transfer Between Spheres

ClassDraft

The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-669 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-669, Incorrect Resource Transfer Between Spheres, 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 FrameworkNational Institute of Standards and Technology

Make elimination of CWE-669 a product outcome

Apply CISA's Secure by Design principle of taking ownership of customer security outcomes to CWE-669, Incorrect Resource Transfer Between Spheres. 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 SoftwareCybersecurity and Infrastructure Security Agency

Connect Incorrect Resource Transfer Between Spheres to documented attack evidence

Recorded impacts include Read Application Data, Modify Application Data, and Unexpected State; observed examples include CVE-2021-22909, CVE-2023-5227, and CVE-2005-0406; related weaknesses include CWE-664. Use these source-defined anchors to turn CWE-669 into implementation, review, and verification checks for the affected component.

CWE-669: Incorrect Resource Transfer Between SpheresMITRE CWE

Apply precise root-cause mapping to CWE-669

Apply MITRE's full root-cause mapping guidance when using CWE-669, Incorrect Resource Transfer Between Spheres. 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 GuidanceMITRE CWE

Validate CWE-669 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-669, Incorrect Resource Transfer Between Spheres. 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 TipsMITRE CWE

Frequently Asked Questions

What is CWE-669: Incorrect Resource Transfer Between Spheres?+

CWE-669: Incorrect Resource Transfer Between Spheres is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.

What are the security consequences of Incorrect Resource Transfer Between Spheres?+

If exploited, CWE-669 (Incorrect Resource Transfer Between Spheres) it can compromise Confidentiality and Integrity, leading to outcomes such as Read Application Data, Modify Application Data and Unexpected State.

Which programming languages are affected by Incorrect Resource Transfer Between Spheres?+

CWE-669 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 Resource Transfer Between Spheres?+

MITRE documents real CVEs mapped to CWE-669, including CVE-2021-22909, CVE-2023-5227 and CVE-2005-0406. 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-669 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.

Learn More

Advertisement