io.netty:netty-codec-dns@4.1.118.Final

  • latest version

    4.2.17.Final

  • latest non vulnerable version

  • first published

    12 years ago

  • latest version published

    7 days ago

  • licenses detected

  • package registry

  • Direct Vulnerabilities

    Known vulnerabilities in the io.netty:netty-codec-dns package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Missing Release of Resource after Effective Lifetime

    Affected versions of this package are vulnerable to Missing Release of Resource after Effective Lifetime in AbstractDnsRecord and DefaultDnsRecordDecoder, where a domain name that violates IDNA rules makes IDN.toASCII() throw before the decoded ByteBuf is assigned to the record's content, leaving the buffer unreleased. An attacker can leak direct memory on each malformed record and exhaust it over sustained traffic by sending DNS records whose domain names violate IDNA rules, contain null bytes in a decompressed name, or otherwise fail to decode. Exploitation affects applications that decode DNS records with Netty's DnsRecordDecoder, such as DnsNameResolver clients processing responses from an attacker-influenced resolver or custom DNS servers, and the leak is incremental, requiring sustained malformed records to exhaust memory.

    How to fix Missing Release of Resource after Effective Lifetime?

    Upgrade io.netty:netty-codec-dns to version 4.1.136.Final, 4.2.16.Final or higher.

    [,4.1.136.Final)[4.2.0.Alpha1,4.2.16.Final)
    • H
    Null Byte Interaction Error (Poison Null Byte)

    Affected versions of this package are vulnerable to Null Byte Interaction Error (Poison Null Byte) due to inadequate validation of domain name labels and lengths in the encodeDomainName and decodeDomainName components. An attacker can cause DNS cache poisoning, bypass domain validation, or trigger excessive memory allocation by supplying specially crafted domain names or malicious DNS responses. This can result in downstream failures, silent truncation of domain names, and parser confusion across different DNS implementations.

    How to fix Null Byte Interaction Error (Poison Null Byte)?

    Upgrade io.netty:netty-codec-dns to version 4.1.133.Final, 4.2.13.Final or higher.

    [,4.1.133.Final)[4.2.0.Alpha1,4.2.13.Final)