<?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, 30 Oct 2026 08:02:10 +0000</lastBuildDate>
    <item>
      <title>GHSA-5pvg-856g-cp85 — Netty has Insufficient Bailiwick Validation for NS Records</title>
      <link>https://db.gcve.eu/vuln/ghsa-5pvg-856g-cp85</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.netty:netty-resolver-dns&lt;/p&gt;
&lt;p&gt;### Summary
Netty&amp;#39;s `DnsResolveContext` insufficiently validates the bailiwick of NS records, enabling DNS Cache Poisoning. An attacker controlling an authoritative name server for a subdomain can poison the cache for parent domains (like `.co.uk`).&lt;/p&gt;
&lt;p&gt;### Details
In `io.netty.resolver.dns.DnsResolveContext.AuthoritativeNameServerList#add` method accepts any NS record from the AUTHORITY section as long as the record&amp;#39;s name is a suffix of the questionName.&lt;/p&gt;
&lt;p&gt;This means if the resolver queries evil.co.uk., it will accept an NS record claiming authority over co.uk.. Subsequently, the `handleWithAdditional` method caches the associated A records from the ADDITIONAL section directly into the `authoritativeDnsServerCache` under the parent domain&amp;#39;s key (co.uk.). This bypasses standard bailiwick rules, where a server authoritative for a subdomain should not be trusted to provide authoritative records for its parent. The poisoned cache is then used for all future resolutions under co.uk..&lt;/p&gt;
&lt;p&gt;The `io.netty.resolver.dns.DnsResolveContext.AuthoritativeNameServerList#cache` method only prevents caching if the record is for the root zone (dots == 1).&lt;/p&gt;
&lt;p&gt;### Impact
DNS Cache Poisoning. Any application using Netty&amp;#39;s DNS resolver is impacted.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.netty:netty-resolver-dns&lt;/p&gt;
&lt;p&gt;### Summary
Netty&amp;#39;s `DnsResolveContext` insufficiently validates the bailiwick of NS records, enabling DNS Cache Poisoning. An attacker controlling an authoritative name server for a subdomain can poison the cache for parent domains (like `.co.uk`).&lt;/p&gt;
&lt;p&gt;### Details
In `io.netty.resolver.dns.DnsResolveContext.AuthoritativeNameServerList#add` method accepts any NS record from the AUTHORITY section as long as the record&amp;#39;s name is a suffix of the questionName.&lt;/p&gt;
&lt;p&gt;This means if the resolver queries evil.co.uk., it will accept an NS record claiming authority over co.uk.. Subsequently, the `handleWithAdditional` method caches the associated A records from the ADDITIONAL section directly into the `authoritativeDnsServerCache` under the parent domain&amp;#39;s key (co.uk.). This bypasses standard bailiwick rules, where a server authoritative for a subdomain should not be trusted to provide authoritative records for its parent. The poisoned cache is then used for all future resolutions under co.uk..&lt;/p&gt;
&lt;p&gt;The `io.netty.resolver.dns.DnsResolveContext.AuthoritativeNameServerList#cache` method only prevents caching if the record is for the root zone (dots == 1).&lt;/p&gt;
&lt;p&gt;### Impact
DNS Cache Poisoning. Any application using Netty&amp;#39;s DNS resolver is impacted.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-5pvg-856g-cp85</guid>
    </item>
  </channel>
</rss>
