Skip to content
VulniPulse
Medium5.3Red Hat Linux

Medium [CVE-2024-3653] Undertow: learningpushhandler can lead to remote memory dos attacks

This medium-severity Red Hat Linux advisory covers CVE-2024-3653 affecting Red Hat build of Quarkus 3.8.6.redhat, Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8, Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9.

CVE-2024-3653 Published Jul 8, 2024Updated by vendor Aug 4, 2026
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A vulnerability was found in Undertow. This issue requires enabling the learning-push handler in the server's config, which is disabled by default, leaving the maxAge config in the handler unconfigured.

The default is -1, which makes the handler vulnerable. If someone overwrites that config, the server is not subject to the attack.

The attacker needs to be able to reach the server with a normal HTTP request.

Affected products named by the advisory: Red Hat build of Quarkus 3.8.6.redhat; Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8; Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9; Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7; and 8 more.

Affected products named by the advisory: OpenShift Serverless; Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Apache Camel for Spring Boot 4; Red Hat build of OptaPlanner 8; and 4 more.

Affected products named by the advisory: Red Hat Data Grid 8; Red Hat Integration Camel K 1; Red Hat Integration Camel Quarkus 2; Red Hat Single Sign-On 7.

Affected versions
  • through 2.3.14.Final

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.