{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5676 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2023-5676 is a medium-severity vulnerability in Eclipse Foundation OpenJ9, published on 15 Nov 2023. 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-2023-5676 and fix it if it is affected.\n\nWhat it is: CVE-2023-5676 is a medium-severity vulnerability in Eclipse Foundation OpenJ9, published on 15 Nov 2023. 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-2023-5676 in the wild and no public exploit code.\n\nAffected product: Eclipse Foundation OpenJ9. 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-2023-5676/ (Markdown: https://insights.sbomify.com/CVE-2023-5676/index.md)","id":"CVE-2023-5676","markdown":"https://insights.sbomify.com/CVE-2023-5676/index.md","name":"CVE-2023-5676","record":{"aliases":["GHSA-5ch2-qvr7-76ch"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Java Virtual Machine","requires_auth":"high_privilege","summary":"An attacker can cause a denial of service by sending a shutdown signal during JVM initialization, leading to an infinite hang or crash.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"openj9","vendor":"eclipse"}],"cvss":{"score":4.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"},{"id":"CWE-364","name":"Signal Handler Race Condition"}],"description":"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.","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 OpenJ9 possible infinite busy hang","id":"CVE-2023-5676","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in AXIS OS","id":"CVE-2023-5677"},"packages":[],"prev":{"headline":"Quarkus: authorization flaw in quarkus resteasy reactive and classic","id":"CVE-2023-5675"},"products":["OpenJ9"],"published":"2023-11-15","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":"2025-11-03","vendors":["Eclipse Foundation"]},"summary":"An attacker can cause a denial of service by sending a shutdown signal during JVM initialization, leading to an infinite hang or crash.","url":"https://insights.sbomify.com/CVE-2023-5676/"}