Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

io.netty:netty

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedMavenPublished

    Netty denial of service vulnerability

    CVE-2014-0193 · GHSA-7vpq-g998-qpv7

    Affected
    • Maven io.netty:netty >= 3.6.0.Beta1, < 3.6.9.Final; >= 3.7.0.Final, < 3.7.1.Final; >= 3.8.0.Final, < 3.8.2.Final; >= 3.9.0.Final, < 3.9.1.Final; >= 4.0.0.Alpha1, < 4.0.19.Final
    Fixed in
    4.0.19.Final3.7.1.Final3.6.9.Final3.9.1.Final3.8.2.Final· Vendor fix available
    Issue
    WebSocket08FrameDecoder in Netty 3.6.x before 3.6.9, 3.7.x before 3.7.1, 3.8.x before 3.8.2, 3.9.x before 3.9.1, and 4.0.x before 4.0.19 allows remote attackers to cause a denial of service (memory consumption) via a TextWebSocketFrame followed by a long stream of ContinuationWebSocketFrames.

    Recommended action: Upgrade to 4.0.19.Final, 3.9.1.Final, 3.8.2.Final or 2 more by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5MavenPublished

    Information Exposure in Netty

    CVE-2015-2156 · GHSA-xfv3-rrfm-f2rv

    Affected
    • Maven io.netty:netty >= 3.10.0, < 3.10.3.Final; < 3.9.8.Final
    Fixed in
    3.9.8.Final3.10.3.Final· Vendor fix available
    Issue
    Netty before 3.9.8.Final, 3.10.x before 3.10.3.Final, 4.0.x before 4.0.28.Final, and 4.1.x before 4.1.0.Beta5 and Play Framework 2.x before 2.3.9 might allow remote attackers to bypass the httpOnly flag on cookies and obtain sensitive information by leveraging improper validation of cookie name and value characters.

    Recommended action: Upgrade to 3.10.3.Final or 3.9.8.Final by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →