<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 20:17:43 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-47703</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-47703</link>
      <description>&lt;p&gt;AdGuard Home is a network-wide software for blocking ads and tracking. Prior to 0.107.75, AdGuard Home&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;AdGuard Home is a network-wide software for blocking ads and tracking. Prior to 0.107.75, AdGuard Home&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-47703</guid>
    </item>
    <item>
      <title>GHSA-xgx4-4h9w-53pv — AdGuard Home: DoQ-to-UDP State Reduction and Source-Port Oracle</title>
      <link>https://db.gcve.eu/vuln/ghsa-xgx4-4h9w-53pv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/AdguardTeam/AdGuardHome, Go: github.com/AdguardTeam/dnsproxy&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;This report covers the client-triggered DoQ forwarding path in:&lt;/p&gt;
&lt;p&gt;- `dnsproxy` `v0.81.2` (`adguard/dnsproxy:v0.81.2`)
- `AdGuard Home` `v0.107.74` (`adguard/adguardhome:latest`, image version label `v0.107.74`)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Attached evidence:&lt;/p&gt;
&lt;p&gt;- `dnsproxy` oracle path on `v0.81.2`: [attachments/artifacts/g03/20260425T141500Z-g03-v0812/summary.txt](attachments/artifacts/g03/20260425T141500Z-g03-v0812/summary.txt)
- `dnsproxy` `v0.81.2` repeatability: [attachments/artifacts/g03/repeatability-v0812.md](attachments/artifacts/g03/repeatability-v0812.md)
- `dnsproxy` steering follow-up on `v0.81.2`: [attachments/artifacts/g04/20260425T141900Z-g04-v0812/summary.txt](attachments/artifacts/g04/20260425T141900Z-g04-v0812/summary.txt)
- `AdGuard Home` oracle path: [attachments/arti…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/AdguardTeam/AdGuardHome, Go: github.com/AdguardTeam/dnsproxy&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;This report covers the client-triggered DoQ forwarding path in:&lt;/p&gt;
&lt;p&gt;- `dnsproxy` `v0.81.2` (`adguard/dnsproxy:v0.81.2`)
- `AdGuard Home` `v0.107.74` (`adguard/adguardhome:latest`, image version label `v0.107.74`)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Attached evidence:&lt;/p&gt;
&lt;p&gt;- `dnsproxy` oracle path on `v0.81.2`: [attachments/artifacts/g03/20260425T141500Z-g03-v0812/summary.txt](attachments/artifacts/g03/20260425T141500Z-g03-v0812/summary.txt)
- `dnsproxy` `v0.81.2` repeatability: [attachments/artifacts/g03/repeatability-v0812.md](attachments/artifacts/g03/repeatability-v0812.md)
- `dnsproxy` steering follow-up on `v0.81.2`: [attachments/artifacts/g04/20260425T141900Z-g04-v0812/summary.txt](attachments/artifacts/g04/20260425T141900Z-g04-v0812/summary.txt)
- `AdGuard Home` oracle path: [attachments/arti…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-xgx4-4h9w-53pv</guid>
    </item>
  </channel>
</rss>
