CVE-2024-58041: Wonko Smolder vulnerability (CVSS 9.1)

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Wonko Smolder≤ 1.51

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://metacpan.org/release/BAREFOOT/Data-Random-0.13/source/lib/Data/Random.pm#L537Issue Tracking
https://metacpan.org/release/WONKO/Smolder-1.51/source/lib/Smolder/DB/Developer.pm#L221Issue Tracking
https://metacpan.org/release/WONKO/Smolder-1.51/source/lib/Smolder/DB/Developer.pm#L5Issue Tracking
https://perldoc.perl.org/functions/randThird Party Advisory
https://security.metacpan.org/docs/guides/random-data-for-security.htmlThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-58041 being actively exploited?

CVE-2024-58041 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.43%.

How severe is CVE-2024-58041?

CVE-2024-58041 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.43% probability of exploitation.

Which products are affected by CVE-2024-58041?

Affected products include Wonko Smolder.

How do I fix CVE-2024-58041?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-58041 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo