# CVE-2017-3319: Information disclosure in MySQL Server

> A low-privileged attacker can exploit a vulnerability in the MySQL Server X Plugin to gain unauthorized read access to a subset of server data.

- **Severity:** Low 3.1 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2017
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-7jfx-rpv3-vwwc, UBUNTU-CVE-2017-3319

## What is CVE-2017-3319?

CVE-2017-3319 is a low-severity vulnerability in Oracle Mysql, published on 27 Jan 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: X Plugin). Supported versions that are affected are 5.7.16 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Server accessible data. CVSS v3.0 Base Score 3.1 (Confidentiality impacts).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-3319?

It affects 1 product.


Products: Oracle Mysql.

## How do I fix CVE-2017-3319?

Upgrade to a fixed version.

## Is CVE-2017-3319 being exploited?

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

What it is: CVE-2017-3319 is a low-severity vulnerability in Oracle Mysql, published on 27 Jan 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3319 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-2017-3319/ (Markdown: https://insights.sbomify.com/CVE-2017-3319/index.md)
```

## Sources

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

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