# CVE-2019-2996: Security feature bypass in Java

> An unauthenticated attacker can bypass Java sandbox restrictions to read and modify data via malicious web content requiring user interaction.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **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 Oct 2019
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-9pp2-vwj5-cwwr, MINI-v5rm-925c-8hf6

## What is CVE-2019-2996?

CVE-2019-2996 is a medium-severity vulnerability in Netapp E-Series Santricity Os Controller, published on 16 Oct 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, Java SE Embedded product of Oracle Java SE (component: Deployment). The supported version that is affected is Java SE: 8u221; Java SE Embedded: 8u221. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Java SE, Java SE Embedded accessible data as well as unauthorized read access to a subset of Java SE, Java SE Embedded accessible data. 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 4.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N).

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

It affects 14 products.


Products: Netapp E-Series Santricity Os Controller, Netapp E-Series Santricity Storage Manager, Netapp E-Series Santricity Unified Manager, Netapp E-Series Santricity Web Services Proxy, 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-2996?

Upgrade to a fixed version.

## Is CVE-2019-2996 being exploited?

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

## Other vulnerabilities in Netapp E-Series Santricity Os Controller

- [CVE-2018-5492](https://insights.sbomify.com/CVE-2018-5492/): Code injection in E-Series SANtricity OS Controller Software (critical 9.8)
- [CVE-2021-26995](https://insights.sbomify.com/CVE-2021-26995/): Code injection in E-Series SANtricity OS Controller Software 11.x (high 8.8)
- [CVE-2021-35560](https://insights.sbomify.com/CVE-2021-35560/): Other in Java SE JDK and JRE (high 7.5)
- [CVE-2021-26996](https://insights.sbomify.com/CVE-2021-26996/): Information disclosure in E-Series SANtricity OS Controller Software 11.x (high 7.5)
- [CVE-2020-8580](https://insights.sbomify.com/CVE-2020-8580/): Denial of service in E-Series SANtricity OS Controller Software (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2996 is a medium-severity vulnerability in Netapp E-Series Santricity Os Controller, published on 16 Oct 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-2996 in the wild and no public exploit code.

Affected product: Netapp E-Series Santricity Os Controller. 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-2996/ (Markdown: https://insights.sbomify.com/CVE-2019-2996/index.md)
```

## Sources

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

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