{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-1471 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-1471 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1471 is a high-severity memory corruption 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-1471 and fix it if it is affected.\n\nWhat it is: CVE-2025-1471 is a high-severity memory corruption 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-1471 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-1471/ (Markdown: https://insights.sbomify.com/CVE-2025-1471/index.md)","id":"CVE-2025-1471","markdown":"https://insights.sbomify.com/CVE-2025-1471/index.md","name":"CVE-2025-1471","record":{"aliases":["GHSA-w5mv-5x6q-jgmp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Eclipse OMR library","requires_auth":"none","summary":"A buffer overflow in Eclipse OMR z/OS print functions allows attackers to cause memory corruption, potentially leading to code execution or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"omr","vendor":"eclipse"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In Eclipse OMR versions 0.2.0 to 0.4.0, some of the z/OS atoe print functions use a constant length buffer for string conversion. If the input format string and arguments are larger than the buffer size then buffer overflow occurs.  Beginning in version 0.5.0, the conversion buffers are sized correctly and checked appropriately to prevent buffer overflows.","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: Buffer overflow vulnerability","id":"CVE-2025-1471","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Unauthorized View Access to Site Statistics and Team Statistics","id":"CVE-2025-1472"},"packages":[],"prev":{"headline":"Eclipse OMR: Null pointer dereference vulnerability","id":"CVE-2025-1470"},"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":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"},{"cvss_score":5.1,"headline":"Eclipse OMR: Null pointer dereference vulnerability","id":"CVE-2025-1470","kev_date_added":null,"published":"2025-02-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":"total"},"state":"PUBLISHED","updated":"2025-02-25","vendors":["Eclipse Foundation"]},"summary":"A buffer overflow in Eclipse OMR z/OS print functions allows attackers to cause memory corruption, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2025-1471/"}