CVE-2020-15237

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 1.0% (61st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Shrine before version 3.3.0, when using the derivation_endpoint plugin, it's possible for the attacker to use a timing attack to guess the signature of the derivation URL. The problem has been fixed by comparing sent and calculated signature in constant time, using Rack::Utils.secure_compare. Users using the derivation_endpoint plugin are urged to upgrade to Shrine 3.3.0 or greater. A possible workaround is provided in the linked advisory.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

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 (value × EchelonGraph’s weight)
Severity59% × 45%
The EG Score, 5.9 of 10.
Exploitation1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default: CISA has not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
1.0%
EPSS %ILE
62nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track or 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 (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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

Published

October 5, 2020

Last Modified

November 21, 2024

References (2)

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
shrine0.9.0 ... 3.2.2 (51 versions)
  • every version up to 3.3.0: fixed in 3.3.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 26× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 89 of 161 refreshes 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. 11 repeat rows among the latest 100 are merged into the row they repeat. The 72 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-10 19:56 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  2. 2026-10-09 20:04 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  3. 2026-10-09 18:25 UTCOSV refresh
  4. 2026-10-08 16:38 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  5. 2026-10-07 23:44 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  6. 2026-10-06 15:13 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  7. 2026-10-05 17:39 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  8. 2026-10-04 23:18 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  9. 2026-10-03 14:22 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  10. 2026-10-02 16:22 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  11. 2026-09-30 15:12 UTCEG score recompute
  12. 2026-09-30 14:59 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  13. 2026-09-27 13:40 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  14. 2026-09-26 15:54 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  15. 2026-09-26 00:20 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  16. 2026-09-24 14:00 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  17. 2026-09-22 14:43 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  18. 2026-09-21 20:28 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  19. 2026-09-20 01:45 UTCOSV refresh
  20. 2026-09-18 19:23 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  21. 2026-09-17 19:22 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  22. 2026-09-16 14:04 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  23. 2026-09-15 03:06 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  24. 2026-09-13 16:42 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  25. 2026-09-12 14:56 UTCEPSS rescoreEPSS 1.0% · 61st percentile
Show 64 more
  1. 2026-09-11 14:48 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  2. 2026-09-11 09:32 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  3. 2026-09-10 09:29 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  4. 2026-09-08 21:56 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  5. 2026-09-07 15:57 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  6. 2026-09-06 13:44 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  7. 2026-09-05 15:24 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  8. 2026-09-04 13:57 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  9. 2026-09-04 05:03 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  10. 2026-09-02 14:08 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  11. 2026-09-01 04:59 UTCOSV refresh
  12. 2026-09-01 03:32 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  13. 2026-08-30 19:14 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  14. 2026-08-30 01:18 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  15. 2026-08-27 14:21 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  16. 2026-08-26 14:42 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  17. 2026-08-25 13:45 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  18. 2026-08-21 23:45 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  19. 2026-08-20 22:52 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  20. 2026-08-19 17:00 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  21. 2026-08-18 13:44 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  22. 2026-08-16 14:52 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  23. 2026-08-16 02:11 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  24. 2026-08-15 04:37 UTCOSV refresh
  25. 2026-08-15 01:26 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  26. 2026-08-13 21:57 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  27. 2026-08-12 13:47 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  28. 2026-08-09 13:43 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  29. 2026-08-08 16:33 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  30. 2026-08-07 16:23 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  31. 2026-08-06 13:43 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  32. 2026-08-05 19:14 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  33. 2026-08-04 15:06 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  34. 2026-08-04 10:34 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  35. 2026-08-03 10:32 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  36. 2026-08-02 02:23 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  37. 2026-08-01 04:12 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  38. 2026-07-30 16:50 UTCOSV refresh
  39. 2026-07-30 16:25 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  40. 2026-07-30 01:27 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  41. 2026-07-28 15:32 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  42. 2026-07-27 14:06 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  43. 2026-07-26 14:51 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  44. 2026-07-25 14:14 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  45. 2026-07-24 14:14 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  46. 2026-07-23 14:15 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  47. 2026-07-23 01:49 UTCEG score recompute
  48. 2026-07-22 22:35 UTCEG score recompute
  49. 2026-07-22 14:05 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  50. 2026-07-21 15:22 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  51. 2026-07-20 17:04 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  52. 2026-07-19 14:28 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  53. 2026-07-19 02:26 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  54. 2026-07-18 10:02 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  55. 2026-07-16 16:59 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  56. 2026-07-15 16:55 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  57. 2026-07-15 01:57 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  58. 2026-07-13 22:27 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  59. 2026-07-13 06:10 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  60. 2026-07-13 01:38 UTCOSV refresh
  61. 2026-07-12 05:44 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  62. 2026-07-11 08:25 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  63. 2026-07-09 19:07 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  64. 2026-07-08 15:12 UTCEPSS rescoreEPSS 1.0% · 58th percentile

Frequently asked(5)

What is CVE-2020-15237?
CVE-2020-15237 is a medium vulnerability published on October 5, 2020. In Shrine before version 3.3.0, when using the derivationendpoint plugin, it's possible for the attacker to use a timing attack to guess the signature of the derivation URL. The problem has been fixed by comparing sent and calculated signature in constant time, using Rack::Utils.securecompare.…
When was the CVE record for CVE-2020-15237 published?
The CVE record for CVE-2020-15237 was published on October 5, 2020. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2020-15237 actively exploited?
CVE-2020-15237 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-15237?
CVE-2020-15237 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2020-15237?
A fix for CVE-2020-15237 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-15237

Explore →

Is Your Infrastructure Affected by CVE-2020-15237?

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