Predictable random values via unset entropy source
Published May 25, 2023 · Updated Feb 13, 2025
Insufficient randomness in c-ares before 1.19.1 allows remote attackers to predict security-sensitive values in Autotools cross-compiled builds. The Autotools configuration leaves CARES_RANDOM_FILE unset during cross-compilation, causing the library to fall back from a cryptographic source to rand(). Exploitation requires a build produced under that condition; the advisory does not identify a specific application-level consequence.
Summary
What happened
Insufficient randomness in c-ares before 1.19.1 allows remote attackers to predict security-sensitive values in Autotools cross-compiled builds. The Autotools configuration leaves CARES_RANDOM_FILE unset during cross-compilation, causing the library to fall back from a cryptographic source to rand(). Exploitation requires a build produced under that condition; the advisory does not identify a specific application-level consequence.
The record
- CVE
- CVE-2023-31124
- Published
- May 25, 2023
- Updated
- Feb 13, 2025
- Vendor
- c-ares Project
- Product
- c-ares
- Classifications
- CWE-330
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=< 1.19.1
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