Vulnerability record · CVE-2023-5676 · published 15 November 2023
CVE-2023-5676: Eclipse openj9 race condition vulnerability
Eclipse · Openj9
In Eclipse OpenJ9 before version 0.41.0, the JVM can be forced into an infinite busy hang on a spinlock or a segmentation fault if a shutdown signal (SIGTERM, SIGINT or SIGHUP) is received before the JVM has finished initializing.
Description
In Eclipse OpenJ9 before version 0.41.0, the JVM can be forced into an infinite busy hang on a spinlock or a segmentation fault if a shutdown signal (SIGTERM, SIGINT or SIGHUP) is received before the JVM has finished initializing.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://github.com/eclipse-openj9/openj9/pull/18085 | Issue TrackingPatch |
| https://gitlab.eclipse.org/security/cve-assignement/-/issues/13 | Vendor Advisory |
| https://github.com/eclipse-openj9/openj9/pull/18085 | Issue TrackingPatch |
| https://gitlab.eclipse.org/security/cve-assignement/-/issues/13 | Vendor Advisory |
| https://security.netapp.com/advisory/ntap-20241108-0002/ |
Track CVE-2023-5676 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2023-5676), CISA KEV, FIRST EPSS (scores of 2026-09-29). This page is refreshed as NVD updates the record.