AdGuard Home: DoQ-to-UDP State Reduction and Source-Port Oracle
AdguardTeam AdGuardHome
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/AdguardTeam/AdGuardHome Go |
|
|
| github.com/AdguardTeam/dnsproxy Go |
|
|
AdguardTeam AdGuardHome
| Product | Affected | Fixed in |
|---|---|---|
| github.com/AdguardTeam/AdGuardHome Go |
|
|
| github.com/AdguardTeam/dnsproxy Go |
|
|
AdGuard Home is a network-wide software for blocking ads and tracking. Prior to 0.107.75, AdGuard Home's client-triggered DoQ forwarding path to a udp:// upstream reduced backend UDP DNS state by producing dns_id=0 or txid=0 and exposed a quoted-port ICMP source-port oracle, weakening DNS response matching for forwarded queries. This issue is fixed in version 0.107.75.
From the CVE record · GitHub_M
Before 0.107.75, AdGuard Home’s client-triggered DoQ forwarding to a udp:// upstream can produce a zero DNS ID or transaction ID and expose a quoted-port ICMP source-port oracle. This weakens DNS response matching for forwarded queries; the input does not specify authentication requirements or user interaction.
Operators of AdGuard Home before 0.107.75 and users of the Go package github.com/AdguardTeam/dnsproxy before 0.81.3 should check their deployments.