CVE-2025-1471 Eclipse OMR: Buffer overflow vulnerability
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.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-1471?
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.
Official 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.
Weakness: CWE-787
Which versions are affected by CVE-2025-1471?
It affects 1 product.
Products include Eclipse Omr.
How do I fix CVE-2025-1471?
No fix has been published for CVE-2025-1471 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2025-1471 being exploited?
There is no known exploitation of CVE-2025-1471 in the wild and no public exploit code.
Other vulnerabilities in Eclipse OMR
- CVE-2019-11773 Privilege escalation in Eclipse OMR
- CVE-2019-11774 Race condition in Eclipse OMR
- CVE-2026-1188 Memory corruption in Eclipse OMR
- CVE-2025-14549 OMR on Z processors Exposing a possible buffer over-read problem
- CVE-2026-16243 Eclipse OMR : arraycmp SIMD implementation does not check if the number of bytes to compare is zero
Sources
Also known as GHSA-w5mv-5x6q-jgmp.