CVE-2017-3599

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 90% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized

Also known asEUVD-2017-12716 (ENISA EUVD) · GHSA-292g-7jqj-vpqr (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 90%
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 90%CVSS: 7.5Exploit: Exploit-DB (verified) · other public PoCExposed services: Not assessed

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.0CRITICALhigh confidence
EG Risk
85
EG Risk 85/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation90% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
90%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
90% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 24, 2017

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Oct 14, 2026
🔬 Proof of concept available. Patch available. Sources: redhat.
Web page

CVE-2017-3599 - PSIRT.COM

http://www.securityfocus.com/bid/97754
Web page🟡 PoC Available

SECFORCE - Security without compromise

https://www.secforce.com/blog/2017/04/cve-2017-3599-pre-auth-mysql-remote-dos/
Web page🟡 PoC Available

MySQL < 5.6.35 / < 5.7.17 - Integer Overflow - Multiple dos Exploit

https://www.exploit-db.com/exploits/41954/
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:2886
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2017:2787

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntumysql-testsuite-5.5 (5.5.55-0ubuntu0.14.04.1) @ trusty2026-11-02ubuntu
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 15× in last 7d / 73× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 164 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 64 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 14:05 UTCEchelonGraph re-scored
  2. 2026-11-12 14:05 UTCVendor advisory
  3. 2026-11-12 14:05 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-11 16:29 UTCEPSS rescoreEPSS 90% · 99th percentile
  5. 2026-11-11 14:59 UTCEchelonGraph re-scored
  6. 2026-11-11 14:59 UTCVendor advisory
  7. 2026-11-11 14:59 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-10 15:55 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  9. 2026-11-09 16:51 UTCEchelonGraph re-scored
  10. 2026-11-09 16:51 UTCVendor advisory
  11. 2026-11-09 16:51 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-11-08 17:47 UTCEchelonGraph re-scored
  13. 2026-11-08 17:47 UTCVendor advisory
  14. 2026-11-08 17:47 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-11-07 18:42 UTCEchelonGraph re-scored
  16. 2026-11-07 18:42 UTCVendor advisory
  17. 2026-11-07 18:42 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-11-06 19:38 UTCEchelonGraph re-scored
  19. 2026-11-06 19:38 UTCVendor advisory
  20. 2026-11-06 19:38 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-06 16:28 UTCEPSS rescoreEPSS 90% · 99th percentile
  22. 2026-11-05 20:34 UTCEchelonGraph re-scored
  23. 2026-11-05 20:34 UTCVendor advisory
  24. 2026-11-05 20:34 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-11-04 21:30 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-04 21:30 UTCVendor advisory
  2. 2026-11-04 21:30 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-04 16:28 UTCEPSS rescoreEPSS 90% · 99th percentile
  4. 2026-11-03 22:24 UTCEchelonGraph re-scored
  5. 2026-11-03 22:24 UTCVendor advisory
  6. 2026-11-03 22:24 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-11-02 23:15 UTCEchelonGraph re-scored
  8. 2026-11-02 23:15 UTCVendor advisory
  9. 2026-11-02 23:15 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-11-02 16:55 UTCOSV refresh
  11. 2026-11-02 16:34 UTCEPSS rescoreEPSS 90% · 99th percentile
  12. 2026-11-02 00:11 UTCEchelonGraph re-scored
  13. 2026-11-02 00:11 UTCVendor advisory
  14. 2026-11-02 00:11 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-11-01 01:06 UTCEchelonGraph re-scored
  16. 2026-11-01 01:06 UTCVendor advisory
  17. 2026-11-01 01:06 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-10-31 01:58 UTCEchelonGraph re-scored
  19. 2026-10-31 01:58 UTCVendor advisory
  20. 2026-10-31 01:58 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-10-30 02:54 UTCEchelonGraph re-scored
  22. 2026-10-30 02:54 UTCVendor advisory
  23. 2026-10-30 02:54 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  24. 2026-10-29 16:27 UTCEPSS rescoreEPSS 90% · 99th percentile
  25. 2026-10-29 03:50 UTCEchelonGraph re-scored
  26. 2026-10-29 03:50 UTCVendor advisory
  27. 2026-10-29 03:50 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  28. 2026-10-28 04:45 UTCEchelonGraph re-scored
  29. 2026-10-28 04:45 UTCVendor advisory
  30. 2026-10-28 04:45 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  31. 2026-10-27 05:41 UTCEchelonGraph re-scored
  32. 2026-10-27 05:41 UTCVendor advisory
  33. 2026-10-27 05:41 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  34. 2026-10-26 02:32 UTCVendor advisory
  35. 2026-10-26 02:32 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  36. 2026-10-25 19:33 UTCEchelonGraph re-scored
  37. 2026-10-25 16:27 UTCEPSS rescoreEPSS 90% · 99th percentile
  38. 2026-10-25 03:28 UTCEchelonGraph re-scored
  39. 2026-10-25 03:28 UTCVendor advisory
  40. 2026-10-25 03:28 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  41. 2026-10-24 04:24 UTCEchelonGraph re-scored
  42. 2026-10-24 04:24 UTCVendor advisory
  43. 2026-10-24 04:24 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  44. 2026-10-23 16:26 UTCEPSS rescoreEPSS 90% · 99th percentile
  45. 2026-10-23 05:19 UTCEchelonGraph re-scored
  46. 2026-10-23 05:19 UTCVendor advisory
  47. 2026-10-23 05:19 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  48. 2026-10-22 06:13 UTCEchelonGraph re-scored
  49. 2026-10-22 06:13 UTCVendor advisory
  50. 2026-10-22 06:13 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  51. 2026-10-21 16:27 UTCEPSS rescoreEPSS 90% · 99th percentile
  52. 2026-10-21 07:04 UTCEchelonGraph re-scored
  53. 2026-10-21 07:04 UTCVendor advisory
  54. 2026-10-21 07:04 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  55. 2026-10-20 07:58 UTCEchelonGraph re-scored
  56. 2026-10-20 07:58 UTCVendor advisory
  57. 2026-10-20 07:58 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  58. 2026-10-19 16:26 UTCEPSS rescoreEPSS 90% · 99th percentile
  59. 2026-10-19 08:53 UTCEchelonGraph re-scored
  60. 2026-10-19 08:53 UTCVendor advisory
  61. 2026-10-19 08:52 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  62. 2026-10-18 09:46 UTCEchelonGraph re-scored
  63. 2026-10-18 09:46 UTCVendor advisory
  64. 2026-10-18 09:45 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  65. 2026-10-17 16:27 UTCEPSS rescoreEPSS 90% · 99th percentile
  66. 2026-10-17 10:39 UTCEchelonGraph re-scored
  67. 2026-10-17 10:39 UTCVendor advisory
  68. 2026-10-17 10:39 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  69. 2026-10-16 11:32 UTCEchelonGraph re-scored
  70. 2026-10-16 11:32 UTCVendor advisory
  71. 2026-10-16 11:32 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  72. 2026-10-15 12:09 UTCEchelonGraph re-scored
  73. 2026-10-15 12:09 UTCVendor advisory
  74. 2026-10-15 12:09 UTCGHSA enrichmentGHSA-292g-7jqj-vpqr · GitHub severity HIGH · GitHub CVSS 7.5
  75. 2026-10-14 16:27 UTCEPSS rescoreEPSS 90% · 99th percentile

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 Exploit-DB entry, 1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-41954✓ verified
    Published May 1, 2017

    MySQL < 5.6.35 / < 5.7.17 - Integer Overflow

    Open source ↗
  • GitHub PoCSECFORCE/CVE-2017-3599
    Published 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-severity vulnerability; its CVE record was 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 made public?
CVE-2017-3599 was made public on April 18, 2017: that is the date its CVE record's CNA, Oracle, gives for when the vulnerability was made public. The CVE record itself was published on April 24, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-3599 actively exploited?
CVE-2017-3599 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 90% probability of exploitation in the next 30 days (99th percentile of EPSS-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 + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2017-3599?
A fix for CVE-2017-3599 is available: update to the fixed version the vendor names in its advisory.

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.