CVE-2024-3933: Eclipse Open J9 With -Xgc:concurrentScavenge on IBM Z, could write/read outside of a buffer
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Eclipse Foundation Open J9 0.44.0.
- Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 7.3.
Low priority for now. Upgrade to Eclipse Foundation Open J9 0.44.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-125
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.3
- CNA · eclipse
- 5.3
- 2.0 point gap
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| eclipse | openj9 | cpe:2.3:a:eclipse:openj9 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- eclipse openj90.13.0 and later · before 0.44.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (eclipse). Independent of NVD's CPE analysis and usually ahead of it.
Eclipse Foundation Open J9
- 0.13.0 and later · before 0.44.0affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.5 | java-1_8_0-ibm | before 1.8.0_sr8.35-150000.3.95.1 | 1.8.0_sr8.35-150000.3.95.1 |
| openSUSE:Tumbleweed | java-1_8_0-openj9 | before 1.8.0.442-1.1 | 1.8.0.442-1.1 |
| openSUSE:Tumbleweed | java-11-openj9 | before 11.0.26.0-1.1 | 11.0.26.0-1.1 |
| SUSE:Linux Enterprise Module for Legacy 15 SP5 | java-1_8_0-ibm | before 1.8.0_sr8.35-150000.3.95.1 | 1.8.0_sr8.35-150000.3.95.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | java-1_8_0-ibm | before 1.8.0_sr8.35-30.129.1 | 1.8.0_sr8.35-30.129.1 |
Same product
eclipse: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-41035In Eclipse Openj9 before version 0.29.0, the JVM does not throw IllegalAccessError for MethodHandles that invoke inaccessible interface meth40Plan
- CVE-2019-11772In Eclipse OpenJ9 prior to 0.15, the String.getBytes(int, int, byte[], int) method does not verify that the provided byte array is non-null 40Plan
- CVE-2018-12549In Eclipse OpenJ9 version 0.11.0, the OpenJ9 JIT compiler may incorrectly omit a null check on the receiver object of an Unsafe call when ac40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-2597May 22, 2023 · In Eclipse Openj9 before version 0.38.0, in the implementation of the shared cache (which is enabled by default in OpenJ9 builds) the size o36Monitor
- ← EarlierCVE-2023-5676Nov 15, 2023 · Eclipse OpenJ9 possible infinite busy hang23Monitor
- Later →CVE-2024-10917Nov 11, 2024 · Eclipse OpenJ9 might return an incorrect value in JNI function GetStringUTFLength21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Eclipse Foundation Open J9 | 0.44.0 | Vendor (CNA) |
| opensuse:java-1_8_0-ibm | 1.8.0_sr8.35-150000.3.95.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:java-1_8_0-openj9 | 1.8.0.442-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:java-11-openj9 | 11.0.26.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:java-1_8_0-ibm | 1.8.0_sr8.35-150000.3.95.1 · SUSE:Linux Enterprise Module for Legacy 15 SP5 | Package registry (OSV) |
| suse:java-1_8_0-ibm | 1.8.0_sr8.35-30.129.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- Low
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.