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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-362 (使用共享资源的并发执行不恰当同步问题(竞争条件)) — Vulnerability Class 693

693 vulnerabilities classified as CWE-362 (使用共享资源的并发执行不恰当同步问题(竞争条件)). AI Chinese analysis included.

CWE-362 represents a concurrency weakness where multiple threads access a shared resource without proper synchronization, creating a timing window for unauthorized modification. Attackers typically exploit this by manipulating execution order to trigger unpredictable behavior, such as privilege escalation or data corruption, by interleaving operations to bypass security checks or overwrite critical values. Developers mitigate this risk by implementing robust synchronization mechanisms, including mutexes, semaphores, or atomic operations, to ensure exclusive access during critical sections. Additionally, adopting thread-safe design patterns and minimizing shared state can significantly reduce the attack surface. By rigorously testing concurrent code paths and enforcing strict access controls, engineers prevent race conditions, ensuring application integrity and stability under high-concurrency scenarios.

MITRE CWE Description
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related: Exclusivity - the code sequence is given exclusive access to the shared resource, i.e., no other code sequence can modify properties of the shared resource before the original sequence has completed execution. Atomicity - the code sequence is behaviorally atomic, i.e., no other thread or process can concurrently execute the same sequence of instructions (or a subset) against the same resource. A race condition exists when an "interfering code sequence" can still access the shared resource, violating exclusivity. The interfering code sequence could be "trusted" or "untrusted." A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.
Common Consequences (4)
Availability DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)
When a race condition makes it possible to bypass a resource cleanup routine or trigger multiple initialization routines, it may lead to resource exhaustion.
Availability DoS: Crash, Exit, or Restart, DoS: Instability
When a race condition allows multiple control flows to access a resource simultaneously, it might lead the product(s) into unexpected states, possibly resulting in a crash.
Confidentiality, Integrity Read Files or Directories, Read Application Data
When a race condition is combined with predictable resource names and loose permissions, it may be possible for an attacker to overwrite or access confidential data (CWE-59).
Access Control Execute Unauthorized Code or Commands, Gain Privileges or Assume Identity, Bypass Protection Mechanism
This can have security implications when the expected synchronization is in security-critical code, such as recording whether a user is authenticated or modifying important state information that should not be influenced by an outsider.
Mitigations (5)
Architecture and Design In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring. Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).
Implementation When using multithreading and operating on shared variables, only use thread-safe functions.
Implementation Use atomic operations on shared variables. Be wary of innocent-looking constructs such as "x++". This may appear atomic at the code layer, but it is actually non-atomic at the instruction layer, since it involves a read, followed by a computation, followed by a write.
Examples (2)
This code could be used in an e-commerce application that supports transfers between accounts. It takes the total amount of the transfer, sends it to the new account, and deducts the amount from the original account.
$transfer_amount = GetTransferAmount(); $balance = GetBalanceFromDatabase(); if ($transfer_amount < 0) { FatalError("Bad Transfer Amount"); } $newbalance = $balance - $transfer_amount; if (($balance - $transfer_amount) < 0) { FatalError("Insufficient Funds"); } SendNewBalanceToDatabase($newbalance); NotifyUser("Transfer of $transfer_amount succeeded."); NotifyUser("New balance: $newbalance");
Bad · Perl
In the following pseudocode, the attacker makes two simultaneous calls of the program, CALLER-1 and CALLER-2. Both callers are for the same user account. CALLER-1 (the attacker) is associated with PROGRAM-1 (the instance that handles CALLER-1). CALLER-2 is associated with PROGRAM-2. CALLER-1 makes a transfer request of 80.00. PROGRAM-1 calls GetBalanceFromDatabase and sets $balance to 100.00 PROGRAM-1 calculates $newbalance as 20.00, then calls SendNewBalanceToDatabase(). Due to high server load, the PROGRAM-1 call to SendNewBalanceToDatabase() encounters a delay. CALLER-2 makes a transfer req
Attack · Other
The following function attempts to acquire a lock in order to perform operations on a shared resource.
void f(pthread_mutex_t *mutex) { pthread_mutex_lock(mutex); /* access shared resource */ pthread_mutex_unlock(mutex); }
Bad · C
int f(pthread_mutex_t *mutex) { int result; result = pthread_mutex_lock(mutex); if (0 != result) return result; /* access shared resource */ return pthread_mutex_unlock(mutex); }
Good · C
CVE ID Title CVSS Severity Published
CVE-2026-19936 Bluetooth Mesh delayable message queue: unsynchronized list access leads to NULL pointer dereference — zephyr 4.8 Medium 2026-10-12
CVE-2026-42689 WordPress Events Manager plugin <= 7.4.7 - Race Condition vulnerability — Events Manager 3.7 Low 2026-10-12
CVE-2026-109279 ImageMagick before 6.9.13-57 and 7.x before 7.1.2-32 Heap Buffer Overflow via Concurrent Security Policy Access — ImageMagick 2.5 Low 2026-10-12
CVE-2026-108830 meetecho janus-gateway VideoRoom janus_videoroom.c race condition — janus-gateway 4.2 Medium 2026-10-12
CVE-2026-19571 Race condition in ITE IT8xxx2 SHI host-command backend lets a second SPI request write an unvalidated length into the in-flight request buffer — zephyr 6.7 Medium 2026-10-09
CVE-2026-84230 IBM Guardium Data Protection is affected by multiple vulnerabilities — Guardium Data Protection 7.5 High 2026-10-08
CVE-2026-84271 IBM Guardium Data Protection Signature Verification Bypass — Guardium Data Protection 7.8 High 2026-10-08
CVE-2026-42698 WordPress Tutor LMS plugin <= 4.1.1 - Race Condition vulnerability — Tutor LMS 5.3 Medium 2026-10-08
CVE-2026-94584 Brocade Fabric OS <10.0.1 竞态条件漏洞 — Fabric OS 2.1 Low 2026-10-08
CVE-2026-94583 Brocade Fabric OS竞态条件漏洞致敏感信息泄露 — Fabric OS 2.1 Low 2026-10-08
CVE-2026-107276 MISP Email OTP Race Condition Allows One-Time Password to Be Consumed by Multiple Concurrent Requests — MISP 6.3 Medium 2026-10-07
CVE-2026-105140 Obot 0.25.0 before 0.25.6 and 0.26.0 before 0.26.1 Race Condition Restores Revoked Group Membership — obot 4.2 Medium 2026-10-07
CVE-2026-106385 Chrome < 155.0.8059.39竞态条件漏洞 — Chrome - - 2026-10-06
CVE-2026-106213 Chrome <155.0.8059.39 WebAudio竞态条件致数据泄露 — Chrome - - 2026-10-06
CVE-2026-106201 Chrome <155.0.8059.39 V8竞态条件远程代码执行漏洞 — Chrome - - 2026-10-06
CVE-2026-106238 Chrome 155.0.8059.39前字体竞争条件漏洞 — Chrome - - 2026-10-06
CVE-2026-106255 Chrome <155.0.8059.39 V8竞争条件漏洞 — Chrome - - 2026-10-06
CVE-2026-106426 Chrome < 155.0.8059.39 字体竞争条件漏洞 — Chrome - - 2026-10-06
CVE-2026-106377 Chrome < 155.0.8059.39 字体竞争条件漏洞 — Chrome - - 2026-10-06
CVE-2026-105773 Canimaan Software ClamXAV local privilege escalation — ClamXAV 7.0 High 2026-10-05
CVE-2026-104714 Apache Struts: Shared message formatter exposes date and time values across concurrent requests — Apache Struts - - 2026-10-05
CVE-2026-104970 Plane: InstanceAdminSignUpEndpoint TOCTOU race allows two concurrent unauthenticated callers to both bootstrap as Plane instance admins — plane 8.1 High 2026-10-05
CVE-2026-105112 Nezha 1.8.0 before 2.3.13 Deadlock DoS via notification-group endpoints — nezha 5.3 Medium 2026-10-03
CVE-2026-104855 Wasmtime: Preemption and traps during bulk operations enable breaking internal VM state — wasmtime 2.0 Low 2026-10-02
CVE-2026-39601 WordPress Booking Calendar plugin <= 11.8.4 - Race Condition vulnerability — Booking Calendar 3.7 Low 2026-10-02
CVE-2026-104057 Podgrab Unauthenticated DoS via Concurrent Map Access in WebSocket Handler — podgrab 7.5 High 2026-10-01
CVE-2026-103282 Ghost 0.5.0 before 6.23.0 Multiple Account Creation via Invite Token — Ghost 4.3 Medium 2026-10-01
CVE-2026-103651 MISP HOTP Token Replay via Stale Session-Cached Counter Allows Second-Factor Authentication Bypass — MISP 7.6 High 2026-10-01
CVE-2026-47565 NVIDIA Linux驱动内核竞态致越界写漏洞 — GeForce 6.4 Medium 2026-09-30
CVE-2026-79625 Improper Synchronization in Monitoring in CODESYS Control Runtime — Control RTE (SL) 8.1 High 2026-09-30

Vulnerabilities classified as CWE-362 (使用共享资源的并发执行不恰当同步问题(竞争条件)) represent 693 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.