CVE-2017-14064

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 9%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

Ruby through 2.2.7, 2.3.x through 2.3.4, and 2.4.x through 2.4.1 can expose arbitrary memory during a JSON.generate call. The issues lies in using strdup in ext/json/ext/generator/generator.c, which will stop after encountering a '\0' byte, returning a pointer to a string of length zero, which is not the length stored in space_len.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
52(Track)
EG Risk 52/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
Severity98% × 45%
Exploitation9% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
9%
EPSS %ILE
95%
KEV
Not listed

Published

August 31, 2017

Last Modified

May 13, 2026

Advisory Details (10)

Auto-updated Jul 26, 2026
Patch available. Sources: redhat, github_commit.
generic

HackerOne

https://hackerone.com/reports/209949
github_commit Patch Available

commit 8f782fd8e181 (flori/json)

Patch available: flori/json v2.12.0 (contains commit 8f782fd8e181)

https://github.com/flori/json/commit/8f782fd8e181d9cfe9387ded43a5ca9692266b85
generic

Bug #13853: Backport request r58323 - Ruby - Ruby Issue Tracking System

https://bugs.ruby-lang.org/issues/13853
redhat Patch Available
https://access.redhat.com/errata/RHSA-2018:0585
redhat Patch Available
https://access.redhat.com/errata/RHSA-2018:0583
redhat Patch Available

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2018:0378
redhat Patch Available
https://access.redhat.com/errata/RHSA-2017:3485
generic
http://www.securitytracker.com/id/1042004
generic
http://www.securitytracker.com/id/1039363
generic
http://www.securityfocus.com/bid/100890

Vendor Advisories for CVE-2017-14064(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturuby2.3-tcltk (2.3.1-2~16.04.5) @ xenial2026-05-20ubuntu
ubunturuby1.9.3 (1.9.3.484-2ubuntu1.5) @ trusty2026-05-20ubuntu
ubunturuby2.3-tcltk (2.3.1-2~16.04.10) @ xenial2026-05-20ubuntu
redhatruby4-0-main-4.0.0-33.3.hum12026-04-17redhat
redhatruby3-3-main-3.3.10-23.1.hum12026-04-09redhat
redhatruby3-4-main-3.4.8-31.1.hum12026-04-09redhat
redhatrh-ruby22-ruby-0:2.2.9-19.el72018-03-26redhat
redhatrh-ruby23-ruby-0:2.3.6-67.el72018-03-26redhat
redhatruby-0:2.0.0.648-33.el7_42018-02-28redhat
redhatrh-ruby24-ruby-0:2.4.2-86.el72017-12-19redhat

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.

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 36× 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.

Showing the most recent 100 of 113 total refreshes for this CVE.

  1. 2026-07-26 14:51 UTCEPSS rescore
  2. 2026-07-25 14:13 UTCEPSS rescore
  3. 2026-07-25 06:11 UTCOSV refresh
  4. 2026-07-23 14:15 UTCEPSS rescore
  5. 2026-07-23 01:27 UTCEG score recompute
  6. 2026-07-22 22:06 UTCEG score recompute
  7. 2026-07-22 14:04 UTCEPSS rescore
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-21 15:21 UTCEPSS rescore
  10. 2026-07-20 17:04 UTCEPSS rescore
  11. 2026-07-20 17:04 UTCEPSS rescore
  12. 2026-07-19 14:28 UTCEPSS rescore
  13. 2026-07-19 14:28 UTCEPSS rescore
  14. 2026-07-19 02:26 UTCEPSS rescore
  15. 2026-07-19 02:26 UTCEPSS rescore
  16. 2026-07-18 10:00 UTCEPSS rescore
  17. 2026-07-16 16:59 UTCEPSS rescore
  18. 2026-07-16 16:59 UTCEPSS rescore
  19. 2026-07-15 16:54 UTCEPSS rescore
  20. 2026-07-15 16:54 UTCEPSS rescore
  21. 2026-07-15 01:56 UTCEPSS rescore
  22. 2026-07-13 22:26 UTCEPSS rescore
  23. 2026-07-12 05:43 UTCEPSS rescore
  24. 2026-07-11 08:24 UTCEPSS rescore
  25. 2026-07-09 19:06 UTCEPSS rescore
Show 75 more
  1. 2026-07-08 15:10 UTCEPSS rescore
  2. 2026-07-08 01:05 UTCOSV refresh
  3. 2026-07-07 13:42 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-28 14:04 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-27 03:05 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-22 14:23 UTCEPSS rescore
  18. 2026-06-22 14:23 UTCEPSS rescore
  19. 2026-06-21 14:54 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-19 19:23 UTCEPSS rescore
  24. 2026-06-19 19:23 UTCEPSS rescore
  25. 2026-06-19 12:55 UTCOSV refresh
  26. 2026-06-18 17:50 UTCEPSS rescore
  27. 2026-06-17 17:50 UTCEPSS rescore
  28. 2026-06-16 17:50 UTCEPSS rescore
  29. 2026-06-15 17:45 UTCEPSS rescore
  30. 2026-06-14 23:14 UTCEPSS rescore
  31. 2026-06-14 23:14 UTCEPSS rescore
  32. 2026-06-13 22:57 UTCEPSS rescore
  33. 2026-06-12 23:09 UTCEPSS rescore
  34. 2026-06-11 13:57 UTCEPSS rescore
  35. 2026-06-10 22:15 UTCEPSS rescore
  36. 2026-06-08 14:14 UTCEPSS rescore
  37. 2026-06-07 15:22 UTCEPSS rescore
  38. 2026-06-07 15:22 UTCEPSS rescore
  39. 2026-06-06 13:45 UTCEPSS rescore
  40. 2026-06-06 13:45 UTCEPSS rescore
  41. 2026-06-05 22:44 UTCEPSS rescore
  42. 2026-06-05 06:08 UTCEPSS rescore
  43. 2026-06-05 06:08 UTCEPSS rescore
  44. 2026-06-04 13:10 UTCEPSS rescore
  45. 2026-06-04 13:10 UTCEPSS rescore
  46. 2026-06-02 20:11 UTCEPSS rescore
  47. 2026-06-02 20:11 UTCEPSS rescore
  48. 2026-06-01 13:49 UTCEPSS rescore
  49. 2026-06-01 13:49 UTCEPSS rescore
  50. 2026-05-31 22:28 UTCEPSS rescore
  51. 2026-05-31 00:14 UTCEPSS rescore
  52. 2026-05-30 20:53 UTCOSV refresh
  53. 2026-05-29 13:41 UTCEPSS rescore
  54. 2026-05-28 13:42 UTCEPSS rescore
  55. 2026-05-28 13:42 UTCEPSS rescore
  56. 2026-05-27 13:38 UTCEPSS rescore
  57. 2026-05-27 13:38 UTCEPSS rescore
  58. 2026-05-26 13:42 UTCEPSS rescore
  59. 2026-05-26 13:42 UTCEPSS rescore
  60. 2026-05-26 07:17 UTCEPSS rescore
  61. 2026-05-26 07:17 UTCEPSS rescore
  62. 2026-05-22 21:15 UTCEPSS rescore
  63. 2026-05-22 21:15 UTCEPSS rescore
  64. 2026-05-22 21:15 UTCEPSS rescore
  65. 2026-05-20 22:37 UTCEPSS rescore
  66. 2026-05-20 22:37 UTCEPSS rescore
  67. 2026-05-20 11:21 UTCEPSS rescore
  68. 2026-05-20 11:21 UTCEPSS rescore
  69. 2026-05-20 08:22 UTCVendor advisory
  70. 2026-05-20 08:22 UTCGHSA enrichment
  71. 2026-05-20 04:12 UTCVendor advisory
  72. 2026-05-20 04:12 UTCGHSA enrichment
  73. 2026-05-20 00:03 UTCVendor advisory
  74. 2026-05-20 00:03 UTCGHSA enrichment
  75. 2026-05-19 19:54 UTCVendor advisory

Frequently asked(5)

What is CVE-2017-14064?
CVE-2017-14064 is a critical vulnerability published on August 31, 2017. Ruby through 2.2.7, 2.3.x through 2.3.4, and 2.4.x through 2.4.1 can expose arbitrary memory during a JSON.generate call. The issues lies in using strdup in ext/json/ext/generator/generator.c, which will stop after encountering a '\0' byte, returning a pointer to a string of length zero, which is…
When was CVE-2017-14064 disclosed?
CVE-2017-14064 was first published in the National Vulnerability Database on August 31, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-14064 actively exploited?
CVE-2017-14064 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9% probability of exploitation in the next 30 days, which ranks it in the top 5.1% of all scored CVEs.
What is the CVSS score of CVE-2017-14064?
CVE-2017-14064 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-14064?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-14064, 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-14064

Explore →

Is Your Infrastructure Affected by CVE-2017-14064?

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

Start Free Scan →Browse All CVEs