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

> A high-privileged attacker with local access can compromise MySQL Server to access critical data or cause a denial of service.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/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:** 27 Jan 2017
- **Updated:** 9 Oct 2024
- **Also known as:** ALPINE-CVE-2017-3265, GHSA-x6m4-gw2j-999q, UBUNTU-CVE-2017-3265

## What is CVE-2017-3265?

CVE-2017-3265 is a medium-severity vulnerability in Debian Debian Linux, published on 27 Jan 2017. 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 5.5.53 and earlier, 5.6.34 and earlier and 5.7.16 and earlier. 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. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all MySQL Server accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS v3.0 Base Score 5.6 (Confidentiality and Availability impacts).

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

It affects 9 products.


Products: Debian Debian Linux, Mariadb Mariadb, Oracle Mysql, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation.

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

Apply the vendor's patch.

## Is CVE-2017-3265 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3265 and fix it if it is affected.

What it is: CVE-2017-3265 is a medium-severity vulnerability in Debian Debian Linux, published on 27 Jan 2017. 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-2017-3265 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-3265/ (Markdown: https://insights.sbomify.com/CVE-2017-3265/index.md)
```

## Sources

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

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