io.netty:netty-codec-http@4.1.59.Final

  • latest version

    4.2.12.Final

  • latest non vulnerable version

  • first published

    13 years ago

  • latest version published

    1 months ago

  • licenses detected

  • package registry

  • Direct Vulnerabilities

    Known vulnerabilities in the io.netty:netty-codec-http 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
    • H
    HTTP Request Smuggling

    io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.

    Affected versions of this package are vulnerable to HTTP Request Smuggling in the parsing of quoted strings within chunked transfer encoding extension values. An attacker can inject arbitrary HTTP requests into a connection by crafting chunk extensions containing carriage return or line feed bytes, leading to parsing discrepancies between the server and RFC-compliant intermediaries.

    How to fix HTTP Request Smuggling?

    Upgrade io.netty:netty-codec-http to version 4.1.132.Final, 4.2.12.Final or higher.

    [,4.1.132.Final)[4.2.0.Alpha1,4.2.12.Final)
    • M
    CRLF Injection

    io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.

    Affected versions of this package are vulnerable to CRLF Injection in HttpRequestEncoder, due to improper sanitization of a URI with line-breaks in the DefaultHttpRequest class. An attacker can manipulate HTTP requests to cause parser desynchronization, request smuggling, and response splitting by including line break characters in requests.

    How to fix CRLF Injection?

    Upgrade io.netty:netty-codec-http to version 4.1.129.Final, 4.2.8.Final or higher.

    [,4.1.129.Final)[4.2.0.Alpha1,4.2.8.Final)
    • H
    Improper Handling of Highly Compressed Data (Data Amplification)

    io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.

    Affected versions of this package are vulnerable to Improper Handling of Highly Compressed Data (Data Amplification) via the BrotliDecoder.decompress function, which has no limit on how often it calls pull, decompressing data 64K bytes at a time. An attacker can exhaust system memory and cause application downtime by submitting specially crafted compressed input that triggers excessive buffer allocations.

    How to fix Improper Handling of Highly Compressed Data (Data Amplification)?

    Upgrade io.netty:netty-codec-http to version 4.1.125.Final or higher.

    [,4.1.125.Final)
    • H
    HTTP Request Smuggling

    io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.

    Affected versions of this package are vulnerable to HTTP Request Smuggling via the parsing of chunk extensions in HTTP/1.1 messages with chunked encoding. An attacker can bypass HTTP request boundaries by sending specially crafted HTTP requests that exploit differences in how standalone newline characters are parsed between reverse proxies and the backend, potentially allowing them to smuggle additional requests.

    How to fix HTTP Request Smuggling?

    Upgrade io.netty:netty-codec-http to version 4.1.125.Final, 4.2.5.Final or higher.

    [,4.1.125.Final)[4.2.0.Alpha1,4.2.5.Final)
    • M
    Allocation of Resources Without Limits or Throttling

    io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.

    Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to the accumulation of data in the HttpPostRequestDecoder. The decoder cumulates bytes in the undecodedChunk buffer until it can decode a field, allowing for data to accumulate without limits.

    An attacker can cause a denial of service by sending a chunked post consisting of many small fields that will be accumulated in the bodyListHttpData list.

    How to fix Allocation of Resources Without Limits or Throttling?

    Upgrade io.netty:netty-codec-http to version 4.1.108.Final or higher.

    [,4.1.108.Final)
    • M
    HTTP Request Smuggling

    io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.

    Affected versions of this package are vulnerable to HTTP Request Smuggling. Netty currently just skips control characters when these are present at the beginning or end of the header name. It should instead fail fast as these are not allowed by the spec and could lead to HTTP request smuggling. Failing to do the validation might cause netty to "sanitize" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore, and therefore does not do the validation itself.

    How to fix HTTP Request Smuggling?

    Upgrade io.netty:netty-codec-http to version 4.1.71.Final or higher.

    [,4.1.71.Final)
    • M
    HTTP Request Smuggling

    io.netty:netty-codec-http is a network application framework for rapid development of maintainable high performance protocol servers & clients.

    Affected versions of this package are vulnerable to HTTP Request Smuggling. If a Content-Length header is present in the original HTTP/2 request, the field is not validated by Http2MultiplexHandler as it is propagated up.

    An additional case of this vulnerability was fixed in 4.1.61.Final (CVE-2021-21409).

    How to fix HTTP Request Smuggling?

    Upgrade io.netty:netty-codec-http to version 4.1.60.Final or higher.

    [,4.1.60.Final)