Crypt::DSA versions before 1.22 for Perl draw the DSA signing nonce and private key from a biased random generator, leading to private-key recovery. "Crypt::DSA::Util::makerandom forces the high bit of every value it returns to obtain an exactly N-bit integer for prime search. Th...
Product
debian/libcrypt-dsa-perl vulnerabilities
5 published CVES affecting debian/libcrypt-dsa-perl, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 1
- High
- 2
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest debian/libcrypt-dsa-perl CVEs
Newest publication first
-
HighCVSS 7.5 EPSS 0.51%
-
CriticalCVSS 9.1 EPSS 0.29%
Crypt::DSA versions before 1.21 for Perl reused the nonce across signatures, leading to private-key recovery. Crypt::DSA::sign caches the per-signature nonce material in the Key object without ever clearing it. The first sign() on a Key object picks a nonce, and every later sign(...
-
MediumCVSS 6.5 EPSS 0.32%
Crypt::DSA versions through 1.19 for Perl use 2-args open, allowing existing files to be modified.
-
HighCVSS 7.3 EPSS 0.36%
Crypt::DSA versions before 1.20 for Perl generate seeds using rand. Seeds were generated using Perl's built-in rand function, which is predictable and unsuitable for security usage.
-
MediumCVSS 5.8 EPSS 2.0%
The Crypt::DSA (aka Crypt-DSA) module 1.17 and earlier for Perl, when /dev/random is absent, uses the Data::Random module, which makes it easier for remote attackers to spoof a signature, or determine the signing key of a signed message, via a brute-force attack.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.