Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 18.89% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2021
CVE-2021-21295High confidence
Possible request smuggling in HTTP/2 due missing validation
netty · io.netty:netty-codec-http2
Official source article: GitHub GHSA-WM47-8V5P-WJPJ ↗. Check the applicable product and release in the original source.
5.9MediumCVSS 3.1
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:High, raised one band.upgradedsince 6 Oct 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs netty io.netty:netty-codec-http2 and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
4 package statesRelease-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | netty | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:4.1.48-3 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | netty | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:4.1.48-3 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | netty | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:4.1.48-3 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | netty | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:4.1.48-3 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
Open-source package ranges3 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Mavenio.netty:netty | ECOSYSTEM: introduced 0 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenio.netty:netty-codec-http2 | ECOSYSTEM: introduced 4.0.0; fixed 4.1.60.Final | 4.1.60.Final | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.jboss.netty:netty | ECOSYSTEM: introduced 0 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2021-21295 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynetty: possible request smuggling in HTTP/2 due missing validation
The vendor explicitly identifies these products as affected by this CVE.
- netty as a component of Red Hat build of Quarkus
- netty as a component of Red Hat JBoss A-MQ 6
- netty as a component of Red Hat JBoss Data Grid 7
- netty as a component of Red Hat JBoss Enterprise Application Platform 5
- netty as a component of Red Hat JBoss Enterprise Application Platform 6
- netty as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack
- netty as a component of Red Hat JBoss Fuse 6
- netty as a component of Red Hat JBoss Operations Network 3
- netty as a component of Red Hat OpenShift Application Runtimes
- openshift3/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 3.11
- openshift4/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 4
- openshift4/ose-logging-elasticsearch6 as a component of Red Hat OpenShift Container Platform 4
- Summary
- 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.
- Remediation
- Before applying this update, ensure all previously released errata relevant to your system have been applied. For details about how to apply this update, see: https://access.redhat.com/articles/11258
CVE-2021-21295 · CSAF 2.0 · revision 1 · finalStackable Product Security TeamStackable Security Advisory for: CVE-2021-21295
The vendor explicitly states that these products are not affected by this CVE.
- pkg:maven/io.netty/netty@3.10.6.Final?type=jar@pkg:oci/druid@sha256%3Aa25242342c9de631789204621733a05297b1f0ad94eb4eac94604295e1a6dd79?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fdruid
- pkg:maven/io.netty/netty@3.10.6.Final?type=jar@pkg:oci/druid@sha256%3A5cd603012618d66d2c46cac48a3ac85da4e55746086d90ddd8773e8d695cd51b?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fdruid
- pkg:maven/io.netty/netty@3.10.6.Final?type=jar@pkg:oci/druid@sha256%3Ace7010c1244bac3f5e36eb886be4a6e76240050a9e39d53331fedf7d333d07ef?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fdruid
- pkg:maven/io.netty/netty@3.10.6.Final?type=jar@pkg:oci/hadoop@sha256%3A735302156d5dce86cd53e7f709902541e051552fd899810f84d3773a256a8ed9?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fhadoop
- pkg:maven/io.netty/netty@3.10.6.Final?type=jar@pkg:oci/hive@sha256%3Aa8b1a4a9043510d5c5ddb6bd75d5b6167379e93369fd70585063244d0273cedd?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fhive
- pkg:maven/io.netty/netty@3.10.6.Final?type=jar@pkg:oci/hive@sha256%3A747d21243f9392c909a162045539e842bcfd5d01479d6c401077fd31fea657d3?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fhive
- pkg:maven/io.netty/netty@3.10.6.Final?type=jar@pkg:oci/hive@sha256%3Ac0d1f430ad316dd1506765643cebed677ad9958f1eb000373c649151858c35a0?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fhive
- pkg:maven/io.netty/netty-codec-http2@4.1.51.Final@pkg:oci/nifi@sha256%3A37dc3275b34ef2d8cbdca70a8cfb1656a48d96543a47ec705940445d857d1089?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fnifi
- pkg:maven/io.netty/netty-codec-http2@4.1.51.Final@pkg:oci/nifi@sha256%3A8532d621c3edefa81940a2a65f707fb13d064542ea3a87092cd939b5cbce02c2?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fnifi
- pkg:maven/io.netty/netty-codec-http2@4.1.51.Final@pkg:oci/nifi@sha256%3Af438103b7c7a8aacbbcacb9df14c314f9304b2788b845a89f6c8867ba08ee6ae?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fnifi
- pkg:maven/io.netty/netty-codec-http2@4.1.51.Final@pkg:oci/nifi@sha256%3A6b63ebf93ddf308084d6121fc9024b07dbc6726572adb1937f574bd647381991?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fnifi
- pkg:maven/io.netty/netty@3.7.0.Final?type=jar@pkg:oci/nifi@sha256%3A6b63ebf93ddf308084d6121fc9024b07dbc6726572adb1937f574bd647381991?arch=amd64&repository_url=oci.stackable.tech%2Fsdp%2Fnifi
- Summary
- 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`.
- Remediation
- No remediation text is recorded.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
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`.
What
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`.
Why
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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`.
Why
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-444 ↗
CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling'). The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- netty as a component of Red Hat build of Quarkus
- netty as a component of Red Hat JBoss A-MQ 6
- netty as a component of Red Hat JBoss Data Grid 7
- netty as a component of Red Hat JBoss Enterprise Application Platform 5
- netty as a component of Red Hat JBoss Enterprise Application Platform 6
- netty as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack
- netty as a component of Red Hat JBoss Fuse 6
- netty as a component of Red Hat JBoss Operations Network 3
- netty as a component of Red Hat OpenShift Application Runtimes
- openshift3/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 3.11
- openshift4/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 4
- openshift4/ose-logging-elasticsearch6 as a component of Red Hat OpenShift Container Platform 4
- openshift4/ose-metering-hadoop as a component of Red Hat OpenShift Container Platform 4
- openshift4/ose-metering-hive as a component of Red Hat OpenShift Container Platform 4
- openshift4/ose-metering-presto as a component of Red Hat OpenShift Container Platform 4
- opendaylight.src as a component of Red Hat OpenStack Platform 10 (Newton)
- opendaylight as a component of Red Hat OpenStack Platform 13 (Queens)
- opendaylight.src as a component of Red Hat OpenStack Platform 13 (Queens)
- Fixed
- eap7-artemis-wildfly-integration-0:1.0.4-1.redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-artemis-wildfly-integration-0:1.0.4-1.redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-bouncycastle-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-bouncycastle-0:1.68.0-2.redhat_00005.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-bouncycastle-mail-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-bouncycastle-pkix-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-bouncycastle-prov-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-hal-console-0:3.2.14-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-hal-console-0:3.2.14-1.Final_redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-infinispan-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-infinispan-0:9.4.22-3.Final_redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-infinispan-cachestore-jdbc-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-infinispan-cachestore-remote-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-infinispan-client-hotrod-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-infinispan-commons-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-infinispan-core-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-infinispan-hibernate-cache-commons-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-infinispan-hibernate-cache-spi-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-infinispan-hibernate-cache-v53-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-ironjacamar-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-ironjacamar-0:1.4.30-1.Final_redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-ironjacamar-common-api-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-ironjacamar-common-impl-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-ironjacamar-common-spi-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-ironjacamar-core-api-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-ironjacamar-core-impl-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-ironjacamar-deployers-common-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-ironjacamar-jdbc-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-ironjacamar-validator-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- eap7-jboss-genericjms-0:2.0.9-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server
- and 376 more
- Action
- Before applying this update, ensure all previously released errata relevant to your system have been applied. For details about how to apply this update, see: https://access.redhat.com/articles/11258
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 9 Mar 2021 · Last source change 3 Aug 2024, 18:09 UTC · CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2021-0719
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- < 4.1.60.Final · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- < 4.1.60.Final · Fixed: Before applying this update, ensure all previously released errata relevant to your system have been applied. For details about how to apply this update, see: https://access.redhat.com/articles/11258
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- netty as a component of Red Hat build of Quarkus; netty as a component of Red Hat JBoss A-MQ 6; netty as a component of Red Hat JBoss Data Grid 7; netty as a component of Red Hat JBoss Enterprise Application Platform 5; netty as a component of Red Hat JBoss Enterprise Application Platform 6; netty as a component of Red Hat JBoss Fuse 6; netty as a component of Red Hat JBoss Operations Network 3; netty as a component of Red Hat OpenShift Application Runtimes; openshift3/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 3.11; openshift4/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-logging-elasticsearch6 as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-metering-hadoop as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-metering-hive as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-metering-presto as a component of Red Hat OpenShift Container Platform 4; opendaylight.src as a component of Red Hat OpenStack Platform 10 (Newton); opendaylight as a component of Red Hat OpenStack Platform 13 (Queens); opendaylight.src as a component of Red Hat OpenStack Platform 13 (Queens) · Fixed: eap7-artemis-wildfly-integration-0:1.0.4-1.redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-artemis-wildfly-integration-0:1.0.4-1.redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-bouncycastle-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-bouncycastle-0:1.68.0-2.redhat_00005.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-bouncycastle-mail-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-bouncycastle-pkix-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-bouncycastle-prov-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-hal-console-0:3.2.14-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-hal-console-0:3.2.14-1.Final_redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-0:9.4.22-3.Final_redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-cachestore-jdbc-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-cachestore-remote-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-client-hotrod-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-commons-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-core-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-hibernate-cache-commons-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-hibernate-cache-spi-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-hibernate-cache-v53-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-0:1.4.30-1.Final_redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-common-api-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-common-impl-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-common-spi-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-core-api-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-core-impl-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-deployers-common-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-jdbc-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-validator-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-jboss-genericjms-0:2.0.9-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; and 376 more
- After
- netty as a component of Red Hat build of Quarkus; netty as a component of Red Hat JBoss A-MQ 6; netty as a component of Red Hat JBoss Data Grid 7; netty as a component of Red Hat JBoss Enterprise Application Platform 5; netty as a component of Red Hat JBoss Enterprise Application Platform 6; netty as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; netty as a component of Red Hat JBoss Fuse 6; netty as a component of Red Hat JBoss Operations Network 3; netty as a component of Red Hat OpenShift Application Runtimes; openshift3/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 3.11; openshift4/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-logging-elasticsearch6 as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-metering-hadoop as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-metering-hive as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-metering-presto as a component of Red Hat OpenShift Container Platform 4; opendaylight.src as a component of Red Hat OpenStack Platform 10 (Newton); opendaylight as a component of Red Hat OpenStack Platform 13 (Queens); opendaylight.src as a component of Red Hat OpenStack Platform 13 (Queens) · Fixed: eap7-artemis-wildfly-integration-0:1.0.4-1.redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-artemis-wildfly-integration-0:1.0.4-1.redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-bouncycastle-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-bouncycastle-0:1.68.0-2.redhat_00005.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-bouncycastle-mail-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-bouncycastle-pkix-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-bouncycastle-prov-0:1.68.0-2.redhat_00005.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-hal-console-0:3.2.14-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-hal-console-0:3.2.14-1.Final_redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-0:9.4.22-3.Final_redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-cachestore-jdbc-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-cachestore-remote-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-client-hotrod-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-commons-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-core-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-hibernate-cache-commons-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-hibernate-cache-spi-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-infinispan-hibernate-cache-v53-0:9.4.22-3.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-0:1.4.30-1.Final_redhat_00001.1.el6eap.src as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-common-api-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-common-impl-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-common-spi-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-core-api-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-core-impl-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-deployers-common-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-jdbc-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-ironjacamar-validator-0:1.4.30-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; eap7-jboss-genericjms-0:2.0.9-1.Final_redhat_00001.1.el6eap.noarch as a component of Red Hat JBoss EAP 7.3 for RHEL 6 Server; and 376 more
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.