{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-3933 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-3933 is a medium-severity memory corruption vulnerability in Eclipse Foundation Open J9, published on 27 May 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-3933 and fix it if it is affected.\n\nWhat it is: CVE-2024-3933 is a medium-severity memory corruption vulnerability in Eclipse Foundation Open J9, published on 27 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-3933 in the wild and no public exploit code.\n\nAffected product: Eclipse Foundation Open J9. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-3933/ (Markdown: https://insights.sbomify.com/CVE-2024-3933/index.md)","id":"CVE-2024-3933","markdown":"https://insights.sbomify.com/CVE-2024-3933/index.md","name":"CVE-2024-3933","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Java Virtual Machine","requires_auth":"low_privilege","summary":"Attackers can read or write outside buffer boundaries in Eclipse OpenJ9 on IBM Z when using concurrent scavenging garbage collection, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"openj9","vendor":"eclipse"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-805","name":"Buffer Access with Incorrect Length Value"},{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Eclipse Open J9 With -Xgc:concurrentScavenge on IBM Z, could write/read outside of a buffer","id":"CVE-2024-3933","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Mercado Pago payments for WooCommerce 7.3.0 - 7.6.1 - Authenticated (Subscriber+) Arbitrary File Download","id":"CVE-2024-3934"},"packages":[],"prev":{"headline":"Totara LMS User Selector cross-site request forgery","id":"CVE-2024-3932"},"products":["Open J9"],"published":"2024-05-27","related":[{"cvss_score":9.8,"headline":"Security feature bypass in Eclipse OMR","id":"CVE-2021-41035","kev_date_added":null,"published":"2021-10-25"},{"cvss_score":9.8,"headline":"Memory corruption in Eclipse OpenJ9","id":"CVE-2020-27221","kev_date_added":null,"published":"2021-01-21"},{"cvss_score":9.8,"headline":"Memory corruption in Eclipse OpenJ9","id":"CVE-2019-11772","kev_date_added":null,"published":"2019-07-17"},{"cvss_score":9.8,"headline":"Memory corruption in Eclipse OpenJ9","id":"CVE-2018-12547","kev_date_added":null,"published":"2019-02-11"},{"cvss_score":9.8,"headline":"Null dereference in Eclipse OpenJ9","id":"CVE-2018-12549","kev_date_added":null,"published":"2019-02-11"},{"cvss_score":9.8,"headline":"Memory corruption in Eclipse OpenJ9","id":"CVE-2018-12548","kev_date_added":null,"published":"2019-01-31"},{"cvss_score":9.1,"headline":"Missing authorization in Eclipse OpenJ9","id":"CVE-2019-17631","kev_date_added":null,"published":"2019-10-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["Eclipse Foundation"]},"summary":"Attackers can read or write outside buffer boundaries in Eclipse OpenJ9 on IBM Z when using concurrent scavenging garbage collection, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2024-3933/"}