Skip to content

CVE-2021-21295

Is CVE-2021-21295 real, exploitable, or a false positive? Here's the community verdict.

Community verdict: No field verdicts yet. Be the first practitioner to weigh in.

signals

public sources

Exploited in wild
Not listed
CISA KEV
Public exploit
None known
Metasploit/EDB/PoC
Base severity
5.9 Medium
CVSS
Exploitation prob.
19%
FIRST EPSS
Weakness
CWE-444
CWE

Moderate signals. Triage by your actual exposure and reachability.

affected packages

GHSA-wm47-8v5p-wjpj · GitHub rates it moderate
  • Mavenio.netty:netty-codec-http2
    Vulnerable
    ≥ 4.0.0, < 4.1.60.Final
    Fixed in
    4.1.60.Final
  • Mavenorg.jboss.netty:netty
    Vulnerable
    all versions
    Fixed in
    no patched version listed
  • Mavenio.netty:netty
    Vulnerable
    all versions
    Fixed in
    no patched version listed

Source: GitHub Advisory Database (CC-BY 4.0), via OSV.dev. Check your lockfile version against the ranges above.

baseline read

auto · not a community verdict

Low signal — verdict needed

Few public signals point to active risk. Whether a scanner hit here is a true or false positive depends on your version and config — community verdicts decide.

Based on CVSS · FIRST EPSS

Confirm or dispute →

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Netty is an open-source, asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. In Netty (io.netty:netty-codec-http2) before version 4.1.60.Final there is a vulnerability that enables 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. This is fine as long as the request is not proxied through as HTTP/1.1. If the request comes in as an HTTP/2 stream, gets converted into the HTTP/1.1 domain objects (`HttpRequest`, `HttpContent`, etc.) via `Http2StreamFrameToHttpObjectCodec `and then sent up to the child channel's pipeline and proxied through a remote peer as HTTP/1.1 this may result in request smuggling. In a proxy case, users may assume the content-length is validated somehow, which is not the case. If the request is forwarded to a backend channel that is a HTTP/1.1 connection, the Content-Length now has meaning and needs to be checked. An attacker can smuggle requests inside the body as it gets downgraded from HTTP/2 to HTTP/1.1. For an example attack refer to the linked GitHub Advisory. Users are only affected if all of this is true: `HTTP2MultiplexCodec` or `Http2FrameCodec` is used, `Http2StreamFrameToHttpObjectCodec` is used to convert to HTTP/1.1 objects, and these HTTP/1.1 objects are forwarded to another remote peer. This has been patched in 4.1.60.Final As a workaround, the user can do the validation by themselves by implementing a custom `ChannelInboundHandler` that is put in the `ChannelPipeline` behind `Http2StreamFrameToHttpObjectCodec`.

Published

Embed this verdict
TruePositive verdict for CVE-2021-21295
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2021-21295/badge.svg)](https://www.truepositive.app/cve/CVE-2021-21295)
HTML
<a href="https://www.truepositive.app/cve/CVE-2021-21295"><img src="https://www.truepositive.app/cve/CVE-2021-21295/badge.svg" alt="TruePositive verdict for CVE-2021-21295"></a>

Live badge that updates automatically as the community verdict changes.

timeline

  1. Published by NVD

Score and exploit changes tracked since .

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: A curated baseline from public sources, shown separately from community verdicts.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    No confirmed in-the-wild exploitation or public exploit was found for this yet. FIRST EPSS estimates about a 19% chance of exploitation in the next 30 days, which is high relative to most CVEs.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-444.