CVE-2017-20240

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM 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.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 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(medium)
EG Risk
31(Track)
EG Risk 31/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
Severity59% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
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
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libcrypt-pbkdf2-perl0.161520-1, 0.161520-2, 0.261630-1, 0.261630-1~deb13u1, 0.261630-1~deb13u1~deb12u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libcrypt-pbkdf2-perl0.161520-20.261630-1~deb13u1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libcrypt-pbkdf2-perl0.161520-2, 0.261630-1~deb13u1~deb12u10.261630-1~deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libcrypt-pbkdf2-perl0.161520-2, 0.261630-1~deb13u1, 0.261630-1~deb13u1~deb12u10.261630-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 66× 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 160 total refreshes for this CVE.

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 75.9% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.