{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-1470 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-1470 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1470 is a medium-severity vulnerability in Eclipse OMR, published on 21 Feb 2025. 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-2025-1470 and fix it if it is affected.\n\nWhat it is: CVE-2025-1470 is a medium-severity vulnerability in Eclipse OMR, published on 21 Feb 2025. 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-2025-1470 in the wild and no public exploit code.\n\nAffected product: Eclipse OMR. 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-2025-1470/ (Markdown: https://insights.sbomify.com/CVE-2025-1470/index.md)","id":"CVE-2025-1470","markdown":"https://insights.sbomify.com/CVE-2025-1470/index.md","name":"CVE-2025-1470","record":{"aliases":["GHSA-pvp4-8q5g-43fg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Eclipse OMR library","requires_auth":"none","summary":"Attackers can cause denial of service via null pointer dereference in Eclipse OMR z/OS port library functions due to unchecked return values.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"omr","vendor":"eclipse"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"In Eclipse OMR, from the initial contribution to version 0.4.0, some OMR internal port library and utilities consumers of z/OS atoe functions do not check their return values for NULL memory pointers or for memory allocation failures.  This can lead to NULL pointer dereference crashes.  Beginning in version 0.5.0, internal OMR consumers of atoe functions handle NULL return values and memory allocation failures correctly.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Eclipse OMR: Null pointer dereference vulnerability","id":"CVE-2025-1470","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Eclipse OMR: Buffer overflow vulnerability","id":"CVE-2025-1471"},"packages":[],"prev":{"headline":"IDOR in Turtek Software's Eyotek","id":"CVE-2025-1469"},"products":["Eclipse OMR"],"published":"2025-02-21","related":[{"cvss_score":7.8,"headline":"Privilege escalation in Eclipse OMR","id":"CVE-2019-11773","kev_date_added":null,"published":"2019-09-12"},{"cvss_score":7.4,"headline":"Race condition in Eclipse OMR","id":"CVE-2019-11774","kev_date_added":null,"published":"2019-09-12"},{"cvss_score":7.1,"headline":"Eclipse OMR: Buffer overflow vulnerability","id":"CVE-2025-1471","kev_date_added":null,"published":"2025-02-21"},{"cvss_score":6.9,"headline":"Memory corruption in Eclipse OMR","id":"CVE-2026-1188","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":6.9,"headline":"OMR on Z processors Exposing a possible buffer over-read problem","id":"CVE-2025-14549","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":5.7,"headline":"Eclipse OMR : arraycmp SIMD implementation does not check if the number of bytes to compare is zero","id":"CVE-2026-16243","kev_date_added":null,"published":"2026-07-21"}],"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-02-21","vendors":["Eclipse Foundation"]},"summary":"Attackers can cause denial of service via null pointer dereference in Eclipse OMR z/OS port library functions due to unchecked return values.","url":"https://insights.sbomify.com/CVE-2025-1470/"}