Improper Interaction Between Multiple Correctly-Behaving Entities

Opis

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.

Inne nazwy

Interaction Error

Emergent Fault

Skutki

• Integrity

  Unexpected State; Varies by Context

Przykłady podatności

• CVE-2002-0485 Anti-virus product allows bypass via Content-Type and Content-Disposition headers that are mixed case, which are still processed by some clients.
• CVE-2003-0411 chain: Code was ported from a case-sensitive Unix platform to a case-insensitive Windows platform where filetype handlers treat .jsp and .JSP as different extensions. JSP source code may be read because .JSP defaults to the filetype "text".

Słabości podrzędne

• CWE-188 Reliance on Data/Memory Layout
• CWE-436 Interpretation Conflict
• CWE-439 Behavioral Change in New Version or Environment
• CWE-1038 Insecure Automated Optimizations

Kiedy powstaje

• Architecture and Design
• Implementation
• Operation

Dotyczy

Not Language-Specific, Not Technology-Specific

Uwagi

Weaknesses related to this Pillar appear to be under-studied, especially with respect to classification schemes. Input from academic and other communities could help identify and resolve gaps or organizational difficulties within CWE.

The "Interaction Error" term, in CWE and elsewhere, is only intended to describe products that behave according to specification. When one or more of the products do not comply with specifications, then it is more likely to be API Abuse (CWE-227) or an interpretation conflict (CWE-436). This distinction can be blurred in real world scenarios, especially when "de facto" standards do not comply with specifications, or when there are no standards but there is widespread adoption. As a result, it can be difficult to distinguish these weaknesses during mapping and classification.

Źródła

1. Insertion, Evasion, and Denial of Service: Eluding Network Intrusion Detection — Thomas H. Ptacek, Timothy N. Newsham, 1998
2. Use of A Taxonomy of Security Faults — Taimur Aslam, Ivan Krsul, Eugene H. Spafford, 1995