Skip to content
Fencer Intel
medium 5.9

CVE-2017-20240 json

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

published 2026-06-12 4 mo ago modified 2026-06-17 4 mo ago also EUVD-2017-18978

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

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.

Patch / fix

  • ARODLAND Crypt::PBKDF2 0.261630
  • libcrypt-pbkdf2-perl Debian 12 0.261630-1~deb13u1~deb12u1
  • libcrypt-pbkdf2-perl Debian 13 0.261630-1~deb13u1
  • libcrypt-pbkdf2-perl Debian 14 0.261630-1

debian advisories DEBIAN-CVE-2017-20240

  • perl-Crypt-PBKDF2 openSUSE Tumbleweed 0.261630-1.1

opensuse advisories openSUSE-SU-2026:11034-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-20240 updated cvss 5.9

perl-Crypt-PBKDF2: information disclosure via timing attack

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

  • ARODLAND Crypt::PBKDF2

Classification

Weakness
  • CWE-208 Observable Timing Discrepancy

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.