VariantIncomplete

CWE-1096Singleton Class Instance Creation without Proper Locking or Synchronization

Category: logic

Description

The product implements a Singleton design pattern but does not use appropriate locking or other synchronization mechanism to ensure that the singleton class is only instantiated once.

Common consequences· 1

  • Other — Reduce Reliability
    This issue can prevent the product from running reliably, e.g. by making the instantiation process non-thread-safe and introducing deadlock (CWE-833) or livelock conditions. If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.

References

  1. https://cwe.mitre.org/data/definitions/1096.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Use of Singleton Pattern Without Synchronization in a Multithreaded Context
CWE
Improper Synchronization
CWE
Unsynchronized Access to Shared Data in a Multithreaded Context
CWE
Missing Synchronization
CWE
Incorrect Synchronization
CWE
Improper Locking
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.