CVE-2023-5676
15.11.2023, 14:15
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.
Affected Products (NVD)
| Vendor | Product | Version |
|---|---|---|
| eclipse | openj9 | 𝑥 < 0.41.0 |
𝑥
= Vulnerable software versions
Red Hat Enterprise Linux Releases
Red Hat Product | |||||
|---|---|---|---|---|---|
| java-1.8.0-ibm |
| ||||
| java-1.8.0-ibm-demo |
| ||||
| java-1.8.0-ibm-devel |
| ||||
| java-1.8.0-ibm-headless |
| ||||
| java-1.8.0-ibm-jdbc |
| ||||
| java-1.8.0-ibm-plugin |
| ||||
| java-1.8.0-ibm-src |
| ||||
| java-1.8.0-ibm-webstart |
|
Common Weakness Enumeration
- CWE-364 - Signal Handler Race ConditionThe software uses a signal handler that introduces a race condition.
- CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')The program contains a code sequence that can run concurrently with other code, and the code sequence 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 that is operating concurrently.