CVE-2022-2053: When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Underto

Q: How do I fix CVE-2022-2053?

integration camel k: mitigate or apply the listed mitigation; jboss fuse: downgrade or apply the listed mitigation; undertow: upgrade to 2.2.19. Exact commands for each OS are on this page.

Q: Is CVE-2022-2053 being exploited?

CVE-2022-2053 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-2053 affect?

CVE-2022-2053 affects integration camel k, jboss fuse, undertow. Severity is high (CVSS 7.5). When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Undertow's AjpServerRequestConduit implementation closes a connection without sending any response to the client/proxy. This behavior res

Q: How urgent is CVE-2022-2053?

Priority 53/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

This month

HIGH 7.5REMOTEWATCHLISTMITIGATEDOWNGRADEUPGRADE

CVE-2022-2053 is a high-severity flaw (CVSS 7.5) affecting integration camel k, jboss fuse, undertow. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Undertow's AjpServerRequestConduit implementation closes a connection without sending any response to the client/proxy. This behavior results in that a front-end proxy marking the backend worker (application server) as an error state and not forward requests to the worker for a while. In mod_cluster, this continues until the next STATUS request

Why this priority

High severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-400
Published	2022-08-05
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: redhat

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-08-05 16:15 UTCPublished CVE record published
2026-06-17 04:41 UTCUpdated Record last modified

redhat integration camel k MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy integration-camel-k || rpm -q integration-camel-k || integration-camel-k --version

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

redhat jboss fuse DOWNGRADE

Affected: 7.0.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.0.0

1. Check installed version

apt-cache policy jboss-fuse || rpm -q jboss-fuse || jboss-fuse --version

2. No fixed release: DOWNGRADE to a release before 7.0.0 (Debian / Ubuntu)

apt-cache madison jboss-fuse sudo apt install jboss-fuse=<VERSION_BEFORE_7.0.0> sudo apt-mark hold jboss-fuse

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list jboss-fuse sudo dnf downgrade jboss-fuse-<VERSION_BEFORE_7.0.0> sudo dnf versionlock add jboss-fuse

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat undertow UPGRADE

Affected: < 2.2.19 · 2.3.0 alpha1

Fixed in: 2.2.19

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy undertow || rpm -q undertow || undertow --version

2. UPGRADE to 2.2.19 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade undertow

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade undertow

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-2053?

integration camel k: mitigate or apply the listed mitigation; jboss fuse: downgrade or apply the listed mitigation; undertow: upgrade to 2.2.19. Exact commands for each OS are on this page.

Is CVE-2022-2053 being exploited?

CVE-2022-2053 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-2053 affect?

CVE-2022-2053 affects integration camel k, jboss fuse, undertow. Severity is high (CVSS 7.5). When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Undertow's AjpServerRequestConduit implementation closes a connection without sending any response to the client/proxy. This behavior res

How urgent is CVE-2022-2053?

Priority 53/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

JBoss and WildFly vulnerabilities

Related CVEs

CVE-2024-7885 HIGH 7.5 MITIGATE MITIGATE A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instan
CVE-2023-4853 HIGH 8.1 UPGRADE DOWNGRADE A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations cor
CVE-2023-1108 HIGH 7.5 MITIGATE DOWNGRADE A flaw was found in undertow
CVE-2022-4492 HIGH 7.5 MITIGATE MITIGATE The undertow client is not checking the server identity presented by the server certificate in https connectio
CVE-2022-4245 MEDIUM 4.3 UPGRADE UPGRADE A flaw was found in codehaus-plexus

References

← Back to latest CVEs