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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

596 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-49803 Windows AppX Deployment Extensions Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.0 High 2026-07-14
CVE-2026-49806 Windows USB Print Driver Elevation of Privilege Vulnerability — Windows 11 Version 24H2 7.0 High 2026-07-14
CVE-2026-49802 Windows USB Print Driver Elevation of Privilege Vulnerability — Windows 11 Version 24H2 7.0 High 2026-07-14
CVE-2026-49183 Windows Clipboard Server Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.0 High 2026-07-14
CVE-2026-44800 Windows Push Notifications Elevation of Privilege Vulnerability — Windows 11 version 23H2 7.8 High 2026-07-14
CVE-2026-58608 Windows Print Spooler Remote Code Execution Vulnerability — Windows 10 Version 1607 8.8 High 2026-07-14
CVE-2026-54999 Windows TCP/IP Remote Code Execution Vulnerability — Windows 10 Version 1607 8.8 High 2026-07-14
CVE-2026-54996 Windows USB Print Driver Elevation of Privilege Vulnerability — Windows 11 Version 24H2 7.0 High 2026-07-14
CVE-2026-54112 Windows Win32k Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High 2026-07-14
CVE-2026-54107 Windows Win32k Elevation of Privilege Vulnerability — Windows 10 Version 1607 8.8 High 2026-07-14
CVE-2026-54991 Windows USB Print Driver Elevation of Privilege Vulnerability — Windows 11 Version 24H2 7.8 High 2026-07-14
CVE-2026-54111 Universal Print Management Service Elevation of Privilege Vulnerability — Windows 11 Version 24H2 7.0 High 2026-07-14
CVE-2026-49784 Microsoft Windows App Store Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.0 High 2026-07-14
CVE-2026-48572 Windows App Package Installer Elevation of Privilege Vulnerability — Windows 11 version 23H2 7.0 High 2026-07-14
CVE-2026-42900 Microsoft Windows App Store Elevation of Privilege Vulnerability — Windows 10 Version 1607 8.1 High 2026-07-14
CVE-2026-57030 Junos OS: SRX Series: Flow sessions are not getting cleared leading to a DoS — Junos OS 5.9 Medium 2026-07-09
CVE-2026-54778 CoreWCF: UnixDomainSocket Non-Reentrant POSIX Identity Resolution — CoreWCF 6.2 Medium 2026-07-08
CVE-2026-59896 hono/jsx does not isolate context per request, leading to cross-request data disclosure — hono 6.5 Medium 2026-07-08
CVE-2026-56297 FreeRDP - Use-After-Free via Race Condition in DRDYNVC Channel Callback — FreeRDP 7.0 High 2026-07-08
CVE-2026-55945 Microsoft Edge (Chromium-based) Information Disclosure Vulnerability — Microsoft Edge (Chromium-based) 4.2 Medium 2026-07-03
CVE-2026-5120 Race Condition vulnerability affecting BIOVIA Workbook from Release 2021 through Release 2026 — BIOVIA Workbook 8.1 High 2026-07-01
CVE-2026-14133 Google Chrome 竞争条件问题漏洞 — Chrome - - 2026-06-30
CVE-2026-14082 Google Chrome 竞争条件问题漏洞 — Chrome - - 2026-06-30
CVE-2026-10654 RFCOMM session-disconnect race leaks session/L2CAP and denies further RFCOMM service in Zephyr Bluetooth Classic — zephyr 3.1 Low 2026-06-30
CVE-2026-46732 Dell Display and Peripheral Manager 竞争条件问题漏洞 — Display and Peripheral Manager 6.7 Medium 2026-06-25
CVE-2026-47386 NocoDB: OAuth Authorization Code Race Condition — nocodb - - 2026-06-23
CVE-2026-48505 Filament: Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission — filament 7.4 High 2026-06-22
CVE-2026-48982 pam_usb: Missing O_EXCL on pad temp file creation allows concurrent update race — pam_usb 5.8 Medium 2026-06-18
CVE-2026-12454 Google Chrome 竞争条件问题漏洞 — Chrome - - 2026-06-17
CVE-2025-13036 Rockwell Automation FactoryTalk Historian Site Edition - Authentication Bypass — FactoryTalk Historian SE - - 2026-06-16

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