CVE-2017-20240

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-06-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Crypt::PBKDF2 versions before 0.261630 for Perl are vulnerable to timing attacks.

These versions use Perl's built-in eq comparison. Discrepancies in timing could be used to guess the underlying derived-key.

CVSS v3
5.9
EG Score
5.9(high)
EPSS
23.8%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 12, 2026

Advisory Details (4)

Auto-updated Jun 15, 2026
No patch confirmed yet. Sources: github_pr.
generic

oss-security - CVE-2017-20240: Crypt::PBKDF2 versions before 0.261630 for Perl are vulnerable to timing attacks

http://www.openwall.com/lists/oss-security/2026/06/12/3
generic

Client Challenge

https://metacpan.org/release/ARODLAND/Crypt-PBKDF2-0.261630/changes
generic

lib/Crypt/PBKDF2.pm - metacpan.org

https://metacpan.org/release/ARODLAND/Crypt-PBKDF2-0.161520/source/lib/Crypt/PBKDF2.pm#L123-148
github_pr

mitigate timing attacks by taking no shortcuts

Upstream fix in progress (PR #6 · arodland/Crypt-PBKDF2, state=open)

https://github.com/arodland/Crypt-PBKDF2/pull/6

Vendor Advisories for CVE-2017-20240(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 81× 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-07 01:15 UTCEG score recompute
  2. 2026-07-07 01:15 UTCGHSA enrichment
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-06 02:20 UTCEPSS rescore
  6. 2026-07-06 02:20 UTCEPSS rescore
  7. 2026-07-05 14:58 UTCEG score recompute
  8. 2026-07-05 14:58 UTCGHSA enrichment
  9. 2026-07-05 02:27 UTCEPSS rescore
  10. 2026-07-04 14:45 UTCEG score recompute
  11. 2026-07-04 14:45 UTCGHSA enrichment
  12. 2026-07-04 06:28 UTCEPSS rescore
  13. 2026-07-03 14:36 UTCEG score recompute
  14. 2026-07-03 14:36 UTCGHSA enrichment
  15. 2026-07-02 16:54 UTCEPSS rescore
  16. 2026-07-02 13:38 UTCEG score recompute
  17. 2026-07-02 13:38 UTCGHSA enrichment
  18. 2026-07-01 15:02 UTCEPSS rescore
  19. 2026-07-01 13:29 UTCEG score recompute
  20. 2026-07-01 13:29 UTCGHSA enrichment
  21. 2026-06-30 23:19 UTCEPSS rescore
  22. 2026-06-30 23:19 UTCEPSS rescore
  23. 2026-06-30 13:20 UTCEG score recompute
  24. 2026-06-30 13:20 UTCGHSA enrichment
  25. 2026-06-29 14:03 UTCEPSS rescore
Show 56 more
  1. 2026-06-29 12:38 UTCEG score recompute
  2. 2026-06-29 12:38 UTCGHSA enrichment
  3. 2026-06-28 14:04 UTCEPSS rescore
  4. 2026-06-28 12:29 UTCEG score recompute
  5. 2026-06-28 12:29 UTCGHSA enrichment
  6. 2026-06-28 04:53 UTCEPSS rescore
  7. 2026-06-27 12:21 UTCEG score recompute
  8. 2026-06-27 12:21 UTCGHSA enrichment
  9. 2026-06-27 03:06 UTCEPSS rescore
  10. 2026-06-27 03:05 UTCEPSS rescore
  11. 2026-06-26 12:13 UTCEG score recompute
  12. 2026-06-26 12:12 UTCGHSA enrichment
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-25 12:04 UTCEG score recompute
  15. 2026-06-25 12:04 UTCGHSA enrichment
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-24 14:02 UTCEPSS rescore
  18. 2026-06-24 11:55 UTCEG score recompute
  19. 2026-06-24 11:55 UTCGHSA enrichment
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-23 11:44 UTCEG score recompute
  22. 2026-06-23 11:43 UTCGHSA enrichment
  23. 2026-06-22 14:23 UTCEPSS rescore
  24. 2026-06-22 14:23 UTCEPSS rescore
  25. 2026-06-22 11:33 UTCEG score recompute
  26. 2026-06-22 11:33 UTCGHSA enrichment
  27. 2026-06-21 14:54 UTCEPSS rescore
  28. 2026-06-21 14:54 UTCEPSS rescore
  29. 2026-06-21 11:24 UTCEG score recompute
  30. 2026-06-21 11:24 UTCGHSA enrichment
  31. 2026-06-21 01:57 UTCEPSS rescore
  32. 2026-06-21 01:57 UTCEPSS rescore
  33. 2026-06-20 11:13 UTCEG score recompute
  34. 2026-06-20 11:13 UTCGHSA enrichment
  35. 2026-06-19 19:23 UTCEPSS rescore
  36. 2026-06-19 19:23 UTCEPSS rescore
  37. 2026-06-19 11:05 UTCEG score recompute
  38. 2026-06-19 11:05 UTCGHSA enrichment
  39. 2026-06-18 17:50 UTCEPSS rescore
  40. 2026-06-18 10:51 UTCEG score recompute
  41. 2026-06-18 10:51 UTCGHSA enrichment
  42. 2026-06-17 17:50 UTCEPSS rescore
  43. 2026-06-17 10:32 UTCEG score recompute
  44. 2026-06-17 10:32 UTCGHSA enrichment
  45. 2026-06-16 17:50 UTCEPSS rescore
  46. 2026-06-16 17:50 UTCEPSS rescore
  47. 2026-06-16 10:20 UTCEG score recompute
  48. 2026-06-16 10:20 UTCGHSA enrichment
  49. 2026-06-15 17:45 UTCEPSS rescore
  50. 2026-06-15 10:12 UTCEG score recompute▲ 5.90
  51. 2026-06-15 10:12 UTCGHSA enrichment
  52. 2026-06-14 23:14 UTCEPSS rescore
  53. 2026-06-13 22:57 UTCEPSS rescore
  54. 2026-06-12 18:12 UTCNVD updateCVSS v3 → 5.9 · severity → MEDIUM
  55. 2026-06-12 16:11 UTCEG score recompute
  56. 2026-06-12 16:11 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2017-20240?
CVE-2017-20240 is a medium vulnerability published on June 12, 2026. Crypt::PBKDF2 versions before 0.261630 for Perl are vulnerable to timing attacks. These versions use Perl's built-in eq comparison. Discrepancies in timing could be used to guess the underlying derived-key.
When was CVE-2017-20240 disclosed?
CVE-2017-20240 was first published in the National Vulnerability Database on June 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-20240 actively exploited?
CVE-2017-20240 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-20240?
CVE-2017-20240 has a CVSS v3.1 base score of 5.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2017-20240?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-20240, 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-20240

Explore →

Is Your Infrastructure Affected by CVE-2017-20240?

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

Start Free Scan →Browse All CVEs