uClibc-ng Vulnerability

[MangoMan]

Vulnerability:

The uClibc and uClibc-ng libraries generate DNS requests with incremental
transaction IDs, while, at the same time, not enforcing any explicit port
randomization techniques during the network connection.
This may result in the possibility for an attacker to perform DNS Cache
Poisoning attacks. More information in the "Exploitability" section here
below.
The vulnerability was confirmed statically and dynamically on version
0.9.33.2. By downloading all releases available on uClibc website, the
vulnerability was confirmed statically in all versions (up to and including
0.9.33.2).
Additionally, by downloading all releases of the uClibc-ng available, the
vulnerability was confirmed statically for this library in all versions (up to
and including 1.0.38, latest available at the time of the research).

https://mailman.openadk.org/mailman3/hyperkitty/list/devel@uclibc-ng.org/thread/6JWRW3P4VN54J5FHUDK7IQOU4V35HHDZ/

[tmomas]

Nozomi DNS poisoning bug affects OpenWrt?

Vanilla OpenWrt is unaffected as it uses musl libc since quite a while, as pointed out by @WereCatf already. Many OEM forks of OpenWrt utilize a version based on Chaos Calmer 15.05 though, which still uses an equally old version of uclibc. Those versions might be affected. Unfortunately the OpenWrt project is not in a position to provide patches for those versions.

[MangoMan]

Thank's for the link, that topic didn't show up in my searches.

Anyhow would it make sense to mention that vulnerabilty here: https://openwrt.org/docs/guide-developer/security even it does not affect recent versions of openwrt?

Sadly the media coverage even mentions openwrt somewhat as affected.