CVE-2024-3933: Eclipse Open J9 With -Xgc:concurrentScavenge on IBM Z, could write/read outside of a buffer
Eclipse Openj9 could allow a local authenticated attacker to bypass security restrictions, caused by the failure to restrict 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. By sending a specially crafted request, an attacker could exploit this vulnerability to gain read and write to addresses beyond the end of the array range.
Other sources
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.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2024-3933?
CVE-2024-3933 is classified as a medium severity vulnerability due to the potential for local authenticated attackers to bypass security restrictions.
How do I fix CVE-2024-3933?
To mitigate CVE-2024-3933, updating to the fixed versions of Eclipse Openj9 or IBM Storage Protect Backup-Archive Client is recommended.
Who is affected by CVE-2024-3933?
CVE-2024-3933 affects users of Eclipse Openj9 versions from 0.13.0 to 0.44.0 and IBM Storage Protect Backup-Archive Client versions up to 8.1.23.0.
What kind of attack does CVE-2024-3933 facilitate?
CVE-2024-3933 allows local authenticated attackers to potentially bypass security restrictions through improper buffer access.
Is there any workaround for CVE-2024-3933?
There are no specific workarounds available for CVE-2024-3933; updating is the recommended action.