Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-1250 — Vulnerability Class 5

5 vulnerabilities classified as CWE-1250. AI Chinese analysis included.

CWE-1250 represents a critical architectural weakness where distributed systems fail to maintain synchronization across independent local copies of shared state. This inconsistency arises when multiple components manage their own caches or data replicas without robust coordination mechanisms, leading to divergent views of the same information. Attackers typically exploit this flaw by manipulating one component’s state while another remains unaware, potentially triggering race conditions, data corruption, or unauthorized access to stale information. To mitigate this risk, developers must implement rigorous consistency protocols, such as distributed locking, versioning schemes, or eventual consistency models with conflict resolution. Regular synchronization checks and comprehensive testing of distributed interactions are essential to ensure that all independent representations remain aligned, thereby preserving data integrity and preventing security vulnerabilities stemming from state divergence.

MITRE CWE Description
The product has or supports multiple distributed components or sub-systems that are each required to keep their own local copy of shared data - such as state or cache - but the product does not ensure that all local copies remain consistent with each other. In highly distributed environments, or on systems with distinct physical components that operate independently, there is often a need for each component to store and update its own local copy of key data such as state or cache, so that all components have the same "view" of the overall system 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 vulnerabilit…
Common Consequences (1)
OtherUnexpected State
One or more of the components/sub-systems could assume that the state is different than it actually is.
Examples (1)
Suppose a processor's Memory Management Unit (MMU) has 5 other shadow MMUs to distribute its workload for its various cores. Each MMU has the start address and end address of "accessible" memory. Any time this accessible range changes (as per the processor's boot status), the main MMU sends an update message to all the shadow MMUs.

Vulnerabilities classified as CWE-1250 represent 5 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.