First published: Wed May 24 2023(Updated: )
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 attacker to take advantage of the lack of entropy by not using a CSPRNG. <a href="https://access.redhat.com/security/cve/CVE-2023-31124">CVE-2023-31124</a>. Low. AutoTools does not set CARES_RANDOM_FILE during cross compilation (<a href="https://github.com/c-ares/c-ares/security/advisories/GHSA-54xr-f67r-4pc4">https://github.com/c-ares/c-ares/security/advisories/GHSA-54xr-f67r-4pc4</a>)
Affected Software | Affected Version | How to fix |
---|---|---|
CwpAPI |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2209494 is potentially high due to the use of a non-cryptographically secure random number generator.
To fix REDHAT-BUG-2209494, ensure that the cross-compilation includes a proper source of entropy for the CSPRNG.
The c-ares library is affected by REDHAT-BUG-2209494 when cross-compiling for certain platforms.
The risks associated with REDHAT-BUG-2209494 include potential exposure to predictability in random number generation, which could be exploited by attackers.
A temporary workaround for REDHAT-BUG-2209494 involves configuring the build system to explicitly set CARES_RANDOM_FILE during cross-compilation.