CVE-2017-3599

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 90% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 90%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 90%CVSS: 7.5Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
91(Track)
EG Risk 91/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation90% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
90%
EPSS %ILE
100%
KEV
Not listed

Published

April 24, 2017

Last Modified

June 17, 2026

References (14)

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumysql-server-5.7 (5.7.18-0ubuntu0.17.04.1) @ zesty2026-05-22ubuntu
redhatrh-mysql57-mysql-0:5.7.19-6.el72017-10-12redhat
redhatrh-mysql56-mysql-0:5.6.37-5.el72017-09-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:29 UTCEG score recompute
  2. 2026-07-22 22:09 UTCEG score recompute
  3. 2026-07-22 14:04 UTCEPSS rescore
  4. 2026-07-22 14:04 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-11 23:52 UTCOSV refresh
  7. 2026-07-09 19:06 UTCEPSS rescore
  8. 2026-07-06 02:20 UTCEPSS rescore
  9. 2026-07-06 02:20 UTCEPSS rescore
  10. 2026-07-05 02:27 UTCEPSS rescore
  11. 2026-06-29 14:03 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-23 21:30 UTCEPSS rescore
  14. 2026-06-23 06:30 UTCOSV refresh
  15. 2026-06-15 17:45 UTCEPSS rescore
  16. 2026-06-12 23:09 UTCEPSS rescore
  17. 2026-06-10 22:15 UTCEPSS rescore
  18. 2026-06-10 13:19 UTCEPSS rescore
  19. 2026-06-06 04:37 UTCOSV refresh
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-05 06:08 UTCEPSS rescore
  23. 2026-06-01 13:49 UTCEPSS rescore
  24. 2026-05-28 13:42 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
Show 8 more
  1. 2026-05-27 13:38 UTCEPSS rescore
  2. 2026-05-27 13:38 UTCEPSS rescore
  3. 2026-05-26 07:17 UTCEPSS rescore
  4. 2026-05-26 07:17 UTCEPSS rescore
  5. 2026-05-22 13:52 UTCEG score recompute
  6. 2026-05-22 13:52 UTCVendor advisory
  7. 2026-05-22 13:52 UTCGHSA enrichment
  8. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-41954✓ verified
    First seen May 1, 2017

    MySQL < 5.6.35 / < 5.7.17 - Integer Overflow

    Open source ↗
  • GitHub PoCSECFORCE/CVE-2017-3599
    First seen Apr 18, 2017

    Proof of concept exploit for CVE-2017-3599

    Open source ↗

Frequently asked(5)

What is CVE-2017-3599?
CVE-2017-3599 is a critical vulnerability published on April 24, 2017. 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…
When was CVE-2017-3599 disclosed?
CVE-2017-3599 was first published in the National Vulnerability Database on April 24, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-3599 actively exploited?
CVE-2017-3599 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
What is the CVSS score of CVE-2017-3599?
CVE-2017-3599 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2017-3599?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-3599, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-3599

Explore →

Is Your Infrastructure Affected by CVE-2017-3599?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs