State Synchronization Error |
Weakness ID: 373 (Weakness Base) | Status: Draft |
Description Summary
Scope | Effect |
---|---|
Depending on the nature of the state of corruption, any of the listed consequences may result. |
Example 1
Phase: Implementation Pay attention to asynchronous actions in processes and make copious use of sanity checks in systems that may be subject to synchronization errors. |
The class of synchronization errors is large and varied, but all rely on the same essential flaw. The state of the system is not what the process expects it to be at a given time. Obviously, the range of possible symptoms is enormous, as is the range of possible solutions. The flaws presented in this section are some of the most difficult to diagnose and fix. It is more important to know how to characterize specific flaws than to gain information about them. |
Nature | Type | ID | Name | View(s) this relationship pertains to![]() |
---|---|---|---|---|
ChildOf | ![]() | 371 | State Issues | Development Concepts (primary)699 |
ChildOf | ![]() | 662 | Insufficient Synchronization | Research Concepts (primary)1000 |
PeerOf | ![]() | 367 | Time-of-check Time-of-use (TOCTOU) Race Condition | Research Concepts1000 |
PeerOf | ![]() | 476 | NULL Pointer Dereference | Research Concepts1000 |
Submissions | ||||
---|---|---|---|---|
Submission Date | Submitter | Organization | Source | |
CLASP | Externally Mined | |||
Modifications | ||||
Modification Date | Modifier | Organization | Source | |
2008-07-01 | Eric Dalci | Cigital | External | |
updated Time of Introduction | ||||
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Common Consequences, Relationships, Other Notes, Taxonomy Mappings |