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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-567 (在多现场上下文中未能对共享数据进行同步访问) — Vulnerability Class 3

3 vulnerabilities classified as CWE-567 (在多现场上下文中未能对共享数据进行同步访问). AI Chinese analysis included.

CWE-567 represents a concurrency weakness where shared data, such as static variables, is accessed by multiple threads without proper synchronization mechanisms. This oversight typically leads to race conditions, resulting in undefined behavior, data corruption, or unpredictable application states. Exploitation often occurs when an attacker triggers concurrent requests that manipulate shared resources simultaneously, potentially bypassing security checks or causing denial of service through inconsistent state. Developers prevent this by implementing thread-safe practices, such as using locks, mutexes, or atomic operations to ensure exclusive access to critical sections. Additionally, avoiding mutable static variables in favor of thread-local storage or immutable objects can mitigate these risks. In frameworks like J2EE, where multithreading is managed automatically, explicit synchronization is crucial to maintain data integrity and prevent subtle, hard-to-reproduce bugs that compromise system reliability.

MITRE CWE Description
The product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes. Within servlets, shared static variables are not protected from concurrent access, but servlets are multithreaded. This is a typical programming mistake in J2EE applications, since the multithreading is handled by the framework. When a shared variable can be influenced by an attacker, one thread could wind up modifying the variable to contain data that is not valid for a different thread that is also using the data within the variable. Note that this weakness is not unique to servlets.
Common Consequences (1)
Confidentiality, Integrity, AvailabilityRead Application Data, Modify Application Data, DoS: Instability, DoS: Crash, Exit, or Restart
If the shared variable contains sensitive data, it may be manipulated or displayed in another user session. If this data is used to control the application, its value can be manipulated to cause the application to crash or perform poorly.
Mitigations (1)
ImplementationRemove the use of static variables used between servlets. If this cannot be avoided, use synchronized access for these variables.
Examples (1)
The following code implements a basic counter for how many times the page has been accesed.
public static class Counter extends HttpServlet { static int count = 0; protected void doGet(HttpServletRequest in, HttpServletResponse out) throws ServletException, IOException { out.setContentType("text/plain"); PrintWriter p = out.getWriter(); count++; p.println(count + " hits so far!"); } }
Bad · Java
CVE IDTitleCVSSSeverityPublished
CVE-2025-48908 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.7 Medium2025-06-06
CVE-2023-44374 Siemens 多款产品 安全漏洞 — RUGGEDCOM RM1224 LTE(4G) EU 6.5 Medium2023-11-14
CVE-2020-25724 Red Hat Quarkus 安全漏洞 — resteasy 7.1 -2021-05-26

Vulnerabilities classified as CWE-567 (在多现场上下文中未能对共享数据进行同步访问) represent 3 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.