Security Resilience

CVE-2023-31124

Crypto Weakness in C-Ares Project C-Ares ≤ 1.19.1

Published
25 May 2023
Modified
13 February 2025
CVSS Score v3.1 3.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0094 62th percentile
Risk Priority 35 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-31124 is a low-severity Use of Insufficiently Random Values (CWE-330) vulnerability in C-Ares Project C-Ares. Its CVSS base score is 3.7 (Low).

Operationally, ranked in the top 38% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

c-ares is an asynchronous resolver library. When cross-compiling c-ares and using the autotools build system, CARES_RANDOM_FILE will not be set, as seen when cross compiling aarch64 android. This will downgrade to using rand() as a fallback which could allow an…

more

attacker to take advantage of the lack of entropy by not using a CSPRNG. This issue was patched in version 1.19.1.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-31147Same product: C-Ares Project C-Ares
CVE-2023-31130Same product: C-Ares Project C-Ares
CVE-2023-32067Same product: C-Ares Project C-Ares
CVE-2019-5420Shared CWE-330
CVE-2024-38273Related weakness
CVE-2024-0813Related weakness
CVE-2024-32662Related weakness
CVE-2023-25193Related weakness
CVE-2023-22840Related weakness
CVE-2024-31142Related weakness

Affected Assets

c-ares project
c-ares
≤ 1.19.1
fedoraproject
fedora
37, 38

Mitigating Controls

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-330

Key generation under controlled management uses approved random-bit sources rather than insufficiently random values.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

blocks

Cryptographic controls require use of approved, sufficiently random values for keys and nonces.

finds

Security testing can detect weak randomness but does not prescribe the control itself.

prevents

Secure coding standards explicitly prohibit use of weak or predictable random number generators.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References