Open J9: Out-of-bounds Read
CVE-2024-3933 is a high-severity out-of-bounds read vulnerability in Open J9 from Eclipse Foundation, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 0.44.0 as the first without the flaw, so updating Open J9 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.21% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Open J9 to 0.44.0 or a later version.
- Update Openj9 to 0.44.0 or a later version.
- Read the advisory on gitlab.eclipse.org for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Eclipse Foundation | Open J9 | 0.13.0 up to, but not including, 0.44.0 | 0.44.0 |
| Eclipse | Openj9 | 0.13.0 up to, but not including, 0.44.0 | 0.44.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 5.3 | Medium | CNA (eclipse.org) |
| CVSS 3.1 | 7.3 | High | NVD |
Official description
In Eclipse OpenJ9 release versions prior to 0.44.0 and after 0.13.0, when running with JVM option -Xgc:concurrentScavenge, the sequence generated for System.arrayCopy on the IBM Z platform with hardware and software support for guarded storage [1], could allow access to a buffer with an incorrect length value when executing an arraycopy sequence while the Concurrent Scavenge Garbage Collection cycle is active and the source and destination memory regions for arraycopy overlap. This allows read and write to addresses beyond the end of the array range.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- gitlab.eclipse.org/security/cve-assignement/-/issues/21Issue Tracking
Patches and release notes
- github.com/eclipse/omr/pull/7275Issue Tracking
Recent Out-of-bounds Read vulnerabilities
- 7.4 High severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 7.1 High severity
- 7.1 High severity
Spotted an error? Tell us.