CWE-435: Improper Interaction Between Multiple Correctly-Behaving Entities

PillarDraft

An interaction error occurs when two entities have correct behavior when running independently of each other, but when they are integrated as components in a larger system or process, they introduce incorrect behaviors that may cause resultant weaknesses.

View on MITRE
Back to CWE Lookup

Extended Description

When a system or process combines multiple independent components, this often produces new, emergent behaviors at the system level. However, if the interactions between these components are not fully accounted for, some of the emergent behaviors can be incorrect or even insecure.

Technical Details

Structure
Simple
Vulnerability Mapping
DISCOURAGED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-435 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-435, Improper Interaction Between Multiple Correctly-Behaving Entities, 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-435 a product outcome

Apply CISA's Secure by Design principle of taking ownership of customer security outcomes to CWE-435, Improper Interaction Between Multiple Correctly-Behaving Entities. 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 Improper Interaction Between Multiple Correctly-Behaving Entities to documented attack evidence

Recorded impacts include Unexpected State, and Varies by Context; observed examples include CVE-2002-0485, and CVE-2003-0411. Use these source-defined anchors to turn CWE-435 into implementation, review, and verification checks for the affected component.

CWE-435: Improper Interaction Between Multiple Correctly-Behaving EntitiesMITRE CWE

Apply precise root-cause mapping to CWE-435

Apply MITRE's full root-cause mapping guidance when using CWE-435, Improper Interaction Between Multiple Correctly-Behaving Entities. 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-435 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-435, Improper Interaction Between Multiple Correctly-Behaving Entities. 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-435: Improper Interaction Between Multiple Correctly-Behaving Entities?+

CWE-435: Improper Interaction Between Multiple Correctly-Behaving Entities is a Common Weakness Enumeration (CWE) entry maintained by MITRE. An interaction error occurs when two entities have correct behavior when running independently of each other, but when they are integrated as components in a larger system or process, they introduce incorrect behaviors that may cause resultant weaknesses. When a system or process combines multiple independent components, this often produces new, emergent behaviors at the system level. However, if the interactions between these components are not fully accounted for, some of the emergent behaviors can be incorrect or even insecure.

What are the security consequences of Improper Interaction Between Multiple Correctly-Behaving Entities?+

If exploited, CWE-435 (Improper Interaction Between Multiple Correctly-Behaving Entities) it can compromise Integrity, leading to outcomes such as Unexpected State and Varies by Context.

Which programming languages are affected by Improper Interaction Between Multiple Correctly-Behaving Entities?+

CWE-435 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 Improper Interaction Between Multiple Correctly-Behaving Entities?+

MITRE documents real CVEs mapped to CWE-435, including CVE-2002-0485 and CVE-2003-0411. 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-435 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