2053
and operate in a coordinated fashion. For example, users of a social media service or a massively
multiplayer online game might be using their own personal computers while also interacting with
different physical hosts in a globally distributed service, but all participants must be able to have the
same "view" of the world. Alternately, a processor's Memory Management Unit (MMU) might have
"shadow" MMUs to distribute its workload, and all shadow MMUs are expected to have the same
accessible ranges of memory.
In such environments, it becomes critical for the product to ensure that this "shared state" is
consistently modified across all distributed systems. If state is not consistently maintained across
all systems, then critical transactions might take place out of order, or some users might not get
the same data as other users. When this inconsistency affects correctness of operations, it can
introduce vulnerabilities in mechanisms that depend on consistent state.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 664 Improper Control of a Resource Through its Lifetime 1454
ParentOf 1249 Application-Level Admin Tool with Inconsistent View of
Underlying Operating System