CVE-2022-30295
First published: Fri May 06 2022(Updated: )
uClibc-ng through 1.0.40 and uClibc through 0.9.33.2 use predictable DNS transaction IDs that may lead to DNS cache poisoning. This is related to a reset of a value to 0x2.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Uclibc Uclibc | <=0.9.33.2 | |
| Uclibc-ng Project Uclibc-ng | <=1.0.40 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-30295?
CVE-2022-30295 is considered to be a high-severity vulnerability due to its potential for DNS cache poisoning.
How do I fix CVE-2022-30295?
To fix CVE-2022-30295, you should update uClibc-ng to version 1.0.41 or higher, or uClibc to version 0.9.33.3 or higher.
What software is affected by CVE-2022-30295?
CVE-2022-30295 affects uClibc-ng versions up to and including 1.0.40 and uClibc versions up to and including 0.9.33.2.
What kind of attack can exploit CVE-2022-30295?
CVE-2022-30295 can be exploited to conduct DNS cache poisoning attacks, which may lead to redirects or spoofing.
Is there any workaround for CVE-2022-30295?
Currently, the best mitigation for CVE-2022-30295 is to patch the affected versions of uClibc or uClibc-ng.
- collector/nvd-api
- collector/nvd-index
- agent/references
- agent/author
- agent/softwarecombine
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/tags
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- vendor/uclibc
- canonical/uclibc uclibc
- version/uclibc uclibc/0.9.33.2
- vendor/uclibc-ng project
- canonical/uclibc-ng project uclibc-ng
- version/uclibc-ng project uclibc-ng/1.0.40