# CVE-2019-2536: Denial of service in MySQL Server

> A high-privileged attacker with local access can cause a complete denial of service in MySQL Server through a difficult-to-exploit packaging vulnerability.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **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-jw5v-gf5h-hgh6

## What is CVE-2019-2536?

CVE-2019-2536 is a medium-severity denial of service vulnerability in Netapp Oncommand Unified Manager, published on 16 Jan 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Packaging). Supported versions that are affected are 8.0.13 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in MySQL Server, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.0 Base Score 5.0 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:C/C:N/I:N/A:H).

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

It affects 10 products.


Products: Netapp Oncommand Unified Manager, Netapp Oncommand Workflow Automation, Netapp Snapcenter, Netapp Storage Automation Store, Oracle Mysql, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Software Collections.

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

Apply the vendor's patch.

## Is CVE-2019-2536 being exploited?

There is no known exploitation of CVE-2019-2536 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-2536 and fix it if it is affected.

What it is: CVE-2019-2536 is a medium-severity denial of service vulnerability in Netapp Oncommand Unified Manager, published on 16 Jan 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-2536 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-2536/ (Markdown: https://insights.sbomify.com/CVE-2019-2536/index.md)
```

## Sources

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

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