# CVE-2019-2449: Denial of service in Java

> An unauthenticated attacker can cause a partial denial of service in Java SE via network access, requiring user interaction.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Jan 2019
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-f342-vvpf-f8xr, MINI-p9cp-cfpj-9wrh

## What is CVE-2019-2449?

CVE-2019-2449 is a low-severity denial of service vulnerability in Netapp Oncommand Unified Manager, published on 16 Jan 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Deployment). The supported version that is affected is Java SE: 8u192. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets (in Java SE 8), that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.0 Base Score 3.1 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L).

## Which versions are affected by CVE-2019-2449?

It affects 11 products.


Products: Netapp Oncommand Unified Manager, Netapp Oncommand Workflow Automation, Netapp Snapmanager, Oracle Jdk, Oracle Jre, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation, Redhat Satellite.

## How do I fix CVE-2019-2449?

Apply the vendor's patch.

## Is CVE-2019-2449 being exploited?

There is no known exploitation of CVE-2019-2449 in the wild and no public exploit code.

## Other vulnerabilities in Netapp Oncommand Unified Manager

- [CVE-2018-5487](https://insights.sbomify.com/CVE-2018-5487/): Code injection in OnCommand Unified Manager for Linux (critical 9.8)
- [CVE-2018-5485](https://insights.sbomify.com/CVE-2018-5485/): Privilege escalation in OnCommand Unified Manager for Windows (high 7.8)
- [CVE-2018-5486](https://insights.sbomify.com/CVE-2018-5486/): Security feature bypass in OnCommand Unified Manager for Linux (high 7.8)
- [CVE-2019-5494](https://insights.sbomify.com/CVE-2019-5494/): Information disclosure in OnCommand Unified Manager 7-Mode (high 7.5)
- [CVE-2019-5495](https://insights.sbomify.com/CVE-2019-5495/): Information disclosure in OnCommand Unified Manager for VMware vSphere,Linux and Windows 7.2 and above (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-2449 and fix it if it is affected.

What it is: CVE-2019-2449 is a low-severity denial of service vulnerability in Netapp Oncommand Unified Manager, published on 16 Jan 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-2449 in the wild and no public exploit code.

Affected product: Netapp Oncommand Unified Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-2449/ (Markdown: https://insights.sbomify.com/CVE-2019-2449/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-2449
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-2449
- OSV: https://osv.dev/vulnerability/CVE-2019-2449

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-2449/
Summaries are generated and may contain mistakes; the official description above is the record.