# CVE-2022-39402: Information disclosure in MySQL Server

> An unauthenticated attacker with local access can read a subset of MySQL Shell data, impacting confidentiality.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2022
- **Updated:** 24 Sep 2024
- **Also known as:** AZL-11216, GHSA-938p-vqgq-8x95, UBUNTU-CVE-2022-39402

## What is CVE-2022-39402?

CVE-2022-39402 is a medium-severity vulnerability in Oracle Mysql, published on 18 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the MySQL Shell product of Oracle MySQL (component: Shell: Core Client). Supported versions that are affected are 8.0.30 and prior. Easily exploitable vulnerability allows unauthenticated attacker with logon to the infrastructure where MySQL Shell executes to compromise MySQL Shell. While the vulnerability is in MySQL Shell, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Shell accessible data. CVSS 3.1 Base Score 4.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N).

## Which versions are affected by CVE-2022-39402?

It affects 1 product.


Products: Oracle Mysql.

## How do I fix CVE-2022-39402?

Upgrade to a fixed version.

## Is CVE-2022-39402 being exploited?

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

## Other vulnerabilities in Oracle Mysql

- [CVE-2016-0639](https://insights.sbomify.com/CVE-2016-0639/): Auth bypass in n/a (critical 9.8)
- [CVE-2003-0150](https://insights.sbomify.com/CVE-2003-0150/): Privilege escalation in n/a (critical 9.0)
- [CVE-2005-2572](https://insights.sbomify.com/CVE-2005-2572/): Denial of service in n/a (high 8.5)
- [CVE-2020-14878](https://insights.sbomify.com/CVE-2020-14878/): Auth bypass in MySQL Server (high 8.0)
- [CVE-2002-0969](https://insights.sbomify.com/CVE-2002-0969/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39402 and fix it if it is affected.

What it is: CVE-2022-39402 is a medium-severity vulnerability in Oracle Mysql, published on 18 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-39402 in the wild and no public exploit code.

Affected product: Oracle Mysql. 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-2022-39402/ (Markdown: https://insights.sbomify.com/CVE-2022-39402/index.md)
```

## Sources

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

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