This report covers the client-triggered DoQ forwarding path in:
dnsproxy v0.81.2 (adguard/dnsproxy:v0.81.2)AdGuard Home v0.107.74 (adguard/adguardhome:latest, image version label v0.107.74)The issue was reproduced on 2026-04-25 with the products configured through
their documented DoQ listener and plain UDP upstream surfaces. The scope is the
internal backend UDP hop created when a DoQ query is forwarded to a udp://
upstream.
On that path, the backend DNS ID is not preserved as an independent source of
entropy. For both products, the backend observer saw dns_id=0 for every
sampled client-triggered query on the tested path. Repeated reruns then showed
the same txid=0 behavior and the same positive source-port oracle on every
sampled run. A separate quoted-port ICMP oracle distinguished the correct
backend UDP source port from a wrong one with a stable, client-visible behavior
change.
Attached evidence:
dnsproxy oracle path on v0.81.2: attachments/artifacts/g03/20260425T141500Z-g03-v0812/summary.txtdnsproxy v0.81.2 repeatability: attachments/artifacts/g03/repeatability-v0812.mddnsproxy steering follow-up on v0.81.2: attachments/artifacts/g04/20260425T141900Z-g04-v0812/summary.txtAdGuard Home oracle path: attachments/artifacts/g05/20260425T113000Z-g05/summary.txtThe observable behavior is consistent across both products:
ID collapses to 0 on the
client-triggered path instead of remaining a fresh per-query variable.0.107.750.81.3Exploitability
AV:NAC:LAT:NPR:NUI:NVulnerable System
VC:NVI:NVA:LSubsequent System
SC:NSI:NSA:N6.9/CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N