{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-28167 exists.","fix":"No fix has been published for CVE-2021-28167 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-28167 is a medium-severity vulnerability in The Eclipse Foundation Eclipse OpenJ9, published on 21 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-28167 and fix it if it is affected.\n\nWhat it is: CVE-2021-28167 is a medium-severity vulnerability in The Eclipse Foundation Eclipse OpenJ9, published on 21 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-28167 exists.\n\nAffected product: The Eclipse Foundation Eclipse 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-2021-28167/ (Markdown: https://insights.sbomify.com/CVE-2021-28167/index.md)","id":"CVE-2021-28167","markdown":"https://insights.sbomify.com/CVE-2021-28167/index.md","name":"CVE-2021-28167","record":{"aliases":["GHSA-wmhf-m2r4-mcrp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java JVM implementation","requires_auth":"none","summary":"Attackers can observe uninitialized static values in Eclipse OpenJ9 by bypassing class initialization via the ConstantPool API.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"openj9","vendor":"eclipse"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-909","name":"Missing Initialization of Resource"}],"description":"In Eclipse Openj9 to version 0.25.0, usage of the jdk.internal.reflect.ConstantPool API causes the JVM in some cases to pre-resolve certain constant pool entries. This allows a user to call static methods or access static members without running the class initialization method, and may allow a user to observe uninitialized values.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in Eclipse OpenJ9","id":"CVE-2021-28167","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Local information disclosure via system temporary directory","id":"CVE-2021-28168"},"packages":[],"prev":{"headline":"Null dereference in Eclipse Mosquitto","id":"CVE-2021-28166"},"products":["Eclipse OpenJ9"],"published":"2021-04-21","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-03","vendors":["The Eclipse Foundation"]},"summary":"Attackers can observe uninitialized static values in Eclipse OpenJ9 by bypassing class initialization via the ConstantPool API.","url":"https://insights.sbomify.com/CVE-2021-28167/"}