Encryption padding prediction via Perl rand
Published Sep 29, 2025 · Updated Sep 29, 2025
Insufficient entropy in Vipin Singh Crypt::RandomEncryption 0.01 allows remote attackers to predict encryption padding. The _random() routine selects every inserted alphanumeric character with Perl's predictable rand(), and encrypt() interleaves those characters with RC4 output before a second RC4 pass. No privileges or user interaction are required when a consuming application exposes ciphertext remotely; the predictable padding weakens the module's added randomization.
Summary
What happened
Insufficient entropy in Vipin Singh Crypt::RandomEncryption 0.01 allows remote attackers to predict encryption padding. The _random() routine selects every inserted alphanumeric character with Perl's predictable rand(), and encrypt() interleaves those characters with RC4 output before a second RC4 pass. No privileges or user interaction are required when a consuming application exposes ciphertext remotely; the predictable padding weakens the module's added randomization.
The record
- CVE
- CVE-2024-58040
- Published
- Sep 29, 2025
- Updated
- Sep 29, 2025
- Vendor
- Vipin Singh
- Product
- Crypt::RandomEncryption
- Classifications
- CWE-331, CWE-338
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 29, 2025CVE publishedPublication date reported by the CVE source.
- Sep 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.01 <=*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo