# CVE-2017-3599: Integer overflow in n/a

> An integer overflow in MySQL Server authentication allows unauthenticated attackers to cause a denial of service via crafted packets.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-292g-7jqj-vpqr, UBUNTU-CVE-2017-3599

## What is CVE-2017-3599?

CVE-2017-3599 is a high-severity vulnerability in Oracle Mysql, published on 24 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Pluggable Auth). Supported versions that are affected are 5.6.35 and earlier and 5.7.17 and earlier. Easily "exploitable" vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Server. 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 7.5 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). NOTE: the previous information is from the April 2017 CPU. Oracle has not commented on third-party claims that this issue is an integer overflow in sql/auth/sql_authentication.cc which allows remote attackers to cause a denial of service via a crafted authentication packet.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Oracle Mysql.

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

Apply the vendor's patch.

## Is CVE-2017-3599 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-3599 exists.

Public exploit code:

- Proof of concept exploit for CVE-2017-3599 (github_poc): https://github.com/SECFORCE/CVE-2017-3599
- A tool to crash MySQL servers with CVE-2017-3599 (github_poc): https://github.com/jptr218/mysql_dos
- MySQL < 5.6.35 / < 5.7.17 - Integer Overflow (exploitdb)
- MySQL < 5.6.35 / < 5.7.17 - Integer Overflow (exploitdb)

## 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-3599 and fix it if it is affected.

What it is: CVE-2017-3599 is a high-severity vulnerability in Oracle Mysql, published on 24 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-3599 exists.

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

## Sources

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

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