Security Advisory

CVE-2022-30295: uClibc Predictable DNS Transaction IDs

Last updated:
  • CVE-2022-30295

CVE-2022-30295 is a weakness in the DNS resolver of uClibc and uClibc-ng: DNS transaction IDs are predictable, so an attacker can forge replies and poison a device's DNS cache. It affects uClibc-ng through 1.0.40 and every uClibc release, NVD scores it 6.5, and CERT/CC lists Digi International embedded modules as affected.

Vulnerability summary

CVSS base score

6.5

Medium severity

EPSS score (FIRST)

11.2%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2022-30295 · Source: NVD

Affected components

ComponentCPEVersion range
uClibc-ng DNS resolver (libc/inet/resolv.c)cpe:2.3:a:uclibc-ng_project:uclibc-ng:*:*:*:*:*:*:*:*NVD: through 1.0.40; fixed in 1.0.41 (2022-05-20, per CERT/CC VU#473698) by commit f73fcb3
uClibc DNS resolvercpe:2.3:a:uclibc:uclibc:*:*:*:*:*:*:*:*NVD: through 0.9.33.2, the last uClibc release; no upstream fix
Digi International ConnectCore 9P 9215 and ConnectME 9210—affected per Digi's vendor statement of 2022-03-22 in CERT/CC VU#473698

What does this mean for affected devices?

Nozomi Networks Labs disclosed CVE-2022-30295 on 2022-05-02. Its write-up says the flaw is "caused by the predictability of transaction IDs included in the DNS requests generated by the library", affects all versions of uClibc and uClibc-ng, and that Nozomi withheld the names of the devices on which it reproduced the bug because no fix existed at the time. NVD adds that the issue "is related to a reset of a value to 0x2", scores it 6.5, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N, CWE-330, and lists uClibc-ng through 1.0.40 and uClibc through 0.9.33.2 (NVD).

CERT/CC's VU#473698 states that the libraries "do not employ any randomization in the DNS Transaction ID (DNS TXID) field" and that uClibc-ng 1.0.41, released 2022-05-20, fixes it. The fix is commit f73fcb3 of 2022-05-10, which replaced the simple counter with "a configurable compile time selection of dns query id generation logics, including random"; its message does not name the CVE, so a changelog search for the CVE number misses it. The original uClibc has had no release since 2012, so devices on 0.9.x need a backport or a library change.

The vendor list in VU#473698, last updated 2023-04-04, shows one affected vendor, 41 not affected and 251 with unknown status. Digi International's statement reads: "We have two active devices using uClibc AND susceptible to this based on version: ConnectCore 9P 9215, ConnectME 9210." Several vendors marked not affected explain why, which helps triage: Actiontec uses glibc, and AVM says all DNS requests from user-space programs pass through a caching resolver with its own transaction ID and source port randomization. CERT/CC recommends keeping such devices off the internet, using DNSSEC-validating recursion where possible, and disabling caching on embedded devices when an upstream caching resolver is available.

CVE-2022-30295 is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13); FIRST EPSS gives it 0.112, the 96.0th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).

In firmware, check two things: whether the image links uClibc or uClibc-ng older than 1.0.41, and whether any process sends DNS queries straight from the C library instead of through a resolver that randomises IDs and ports. Our glibc, uClibc and musl guide covers identifying the library, CVE-2021-43523 is the other uClibc DNS flaw, and CVE-2020-25684 is the dnsmasq DNSpooq cache poisoning bug, from the dnsmasq guide.

How to fix this class of issueThis advisory's weakness class is Weak cryptography. Our practical guide covers how to detect, fix, verify and disclose it: How to fix weak cryptography in embedded firmware.

Evidence

  • Disclosed 2022-05-02; predictable transaction IDs; all uClibc/uClibc-ng versions; device names withheld because unpatched; updated to note 1.0.41 fix. — Nozomi Networks Labs
  • NVD Primary CVSS 3.1 6.5 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N), CWE-330; uClibc-ng through 1.0.40, uClibc through 0.9.33.2; related to a reset of a value to 0x2. — NVD
  • No randomization of DNS TXID; uClibc-ng 1.0.41 released 2022-05-20; vendor list 1 affected (Digi), 41 not affected, 251 unknown; Digi names ConnectCore 9P 9215 and ConnectME 9210; last updated 2023-04-04; best practices. — CERT/CC VU#473698
  • Commit f73fcb3 (2022-05-10) adds configurable, random-by-default DNS query ID generation; message does not name the CVE. — uClibc-ng commit f73fcb3
  • Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.11205 (96.0th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CERT/CC VU#473698: uClibc and uClibc-ng predictable DNS transaction IDs
  3. Nozomi Networks Labs: unpatched DNS bug in popular C standard library
  4. uClibc-ng commit f73fcb3: configurable dnsQueryId generation including random
  5. CISA KEV
  6. FIRST EPSS

Frequently asked questions

Which version fixes CVE-2022-30295?

uClibc-ng 1.0.41, released 2022-05-20, which generates random DNS query IDs by default. The original uClibc stopped at 0.9.33.2 and has no fix (per CERT/CC VU#473698 and the uClibc-ng commit).

Which devices are affected by CVE-2022-30295?

In CERT/CC's vendor list, Digi International is the only vendor marked affected, naming the ConnectCore 9P 9215 and ConnectME 9210. The other vendors listed are marked not affected (41) or unknown (251) (per CERT/CC VU#473698).

Is a device safe if it uses a caching DNS resolver?

It can be. AVM told CERT/CC its products are not affected because all user-space DNS requests go through a caching resolver that randomises transaction IDs and source ports on its own. That only holds if no program queries DNS servers directly (per CERT/CC VU#473698).

Is CVE-2022-30295 exploited?

It is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.112, the 96.0th percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).