# CVE-2019-2692: Privilege escalation in mysql-connector-jav

> A high-privileged attacker with local access can compromise the MySQL Connector/J library, leading to full takeover of the component.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/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:** 23 Apr 2019
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-jcq3-cprp-m333, OESA-2022-1547, OESA-2022-2076

## What is CVE-2019-2692?

CVE-2019-2692 is a medium-severity vulnerability in Oracle Corporation MySQL Connectors, published on 23 Apr 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 Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.15 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).

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

2 open source packages ship an affected version, including mysql:mysql-connector-java. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mysql:mysql-connector-java` | Maven | All versions | 8.0.16 |
| `mysql:mysql-connector-java` | Maven | All versions | 8.0.16 |

Products: Oracle Mysql Connector\/J.

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

Upgrade mysql:mysql-connector-java to 8.0.16 or later.

## Is CVE-2019-2692 being exploited?

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

## Other vulnerabilities in Oracle Corporation MySQL Connectors

- [CVE-2026-60586](https://insights.sbomify.com/CVE-2026-60586/): Missing authorization in MySQL Connectors (high 7.7)
- [CVE-2025-30706](https://insights.sbomify.com/CVE-2025-30706/): Privilege escalation in MySQL Connectors (high 7.5)
- [CVE-2026-60623](https://insights.sbomify.com/CVE-2026-60623/): Missing authorization in MySQL Connectors (high 7.1)
- [CVE-2026-60624](https://insights.sbomify.com/CVE-2026-60624/): Denial of service in MySQL Connectors (medium 6.5)
- [CVE-2026-61082](https://insights.sbomify.com/CVE-2026-61082/): Open redirect in MySQL Connectors (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2692 is a medium-severity vulnerability in Oracle Corporation MySQL Connectors, published on 23 Apr 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-2692 in the wild and no public exploit code.

Affected packages and fixed versions:
- mysql:mysql-connector-java (Maven): affected all versions; fixed in 8.0.16
- mysql:mysql-connector-java (Maven): affected all versions; fixed in 8.0.16

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-2692/ (Markdown: https://insights.sbomify.com/CVE-2019-2692/index.md)
```

## Sources

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

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