# What is CVE-2025-1470? > CVE-2025-1470 is a medium-severity flaw (CVSS 5.5) in Omr from Eclipse, published on 21 February 2025. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.2%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2025-1470 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 19 out of 100 (Info); action: Track. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 5.5 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 0.2% (latest exploit-likelihood forecast) - **Published:** 21 February 2025 - **Record last updated:** 5 March 2025 - **Main product:** Omr from Eclipse - **Affected products:** 1 ## What is CVE-2025-1470? In plain terms An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can take it offline. ### The official 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 kind of flaw is it? - CWE-476: NULL Pointer Dereference ### How an attack on it works - Where an attacker can be: Already on the device - How hard it is to pull off: Easy: no special conditions - Login needed first: An ordinary user account - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can take it offline Severity vector: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` ## Is CVE-2025-1470 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.2%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 0.2%, 0.2%, 0.2%, 0.2%, 0.2%, 0.2%, 0.2%. ### Timeline - 21 February 2025: Published - 5 March 2025: Record last updated ### How Precursor Intelligence ranks it CVE-2025-1470 scores **19 out of 100 (Info)**, with the action "Track". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2025-1470? The published record lists 1 product. - [Omr](https://www.precursorintelligence.com/product/eclipse/omr) by [Eclipse](https://www.precursorintelligence.com/vendors/eclipse) (Application): up to 0.4.0 ## How do I fix CVE-2025-1470? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [github.com](https://github.com/eclipse-omr/omr/pull/7655) (Patch) - [github.com](https://github.com/eclipse-omr/omr/pull/7663) (Patch) - [gitlab.eclipse.org](https://gitlab.eclipse.org/security/cve-assignement/-/issues/54) (Issue tracking, Vendor advisory) ## Questions ### What is CVE-2025-1470? CVE-2025-1470 is a medium-severity flaw in Omr from Eclipse, published on 21 February 2025. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can take it offline. ### How serious is CVE-2025-1470? It scores 5.5 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2025-1470 is 19 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2025-1470 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.2%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2025-1470 affect? For Omr from Eclipse: up to 0.4.0. ### How do I fix CVE-2025-1470? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2025-1470 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact