CVE-2024-58041 json
Smolder versions through 1.51 for Perl uses insecure rand() function for cryptographic functions
published 8mo ago modified 4mo ago also EUVD-2024-55433
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
Smolder versions through 1.51 for Perl uses insecure rand() function for cryptographic functions.
Smolder 1.51 and earlier for Perl uses the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions.
Specifically Smolder::DB::Developer uses the Data::Random library which specifically states that it is "Useful mostly for test programs". Data::Random uses the rand() function.
Is CVE-2024-58041 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8mo ago
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected products
- WONKO Smolder
Classification
- Weakness
-
- CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
References
-
perldoc.perl.org
/functions/rand
third-party-advisory
-
security.metacpan.org
/docs/guides/random-data-for-security.html
third-party-advisory
-
metacpan.org
/release/BAREFOOT/Data-Random-0.13/source/lib/Data/Random.pm#L537
issue-tracking
-
metacpan.org
/release/WONKO/Smolder-1.51/source/lib/Smolder/DB/Developer.pm#L5
issue-tracking
-
metacpan.org
/release/WONKO/Smolder-1.51/source/lib/Smolder/DB/Developer.pm#L221
issue-tracking
Sources
- CVE List CVE-2024-58041
- NVD CVE-2024-58041
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.