Vmware Spring Framework up to 5.3.37/6.0.22/6.1.11 Conditional HTTP Request ETags denial of service

Summaryinfo

A vulnerability labeled as critical has been found in Vmware Spring Framework up to 5.3.37/6.0.22/6.1.11. Affected is an unknown function of the component Conditional HTTP Request Handler. The manipulation of the argument ETags results in denial of service. This vulnerability is reported as CVE-2024-38809. The attack can be launched remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical has been found in Vmware Spring Framework up to 5.3.37/6.0.22/6.1.11. Affected is an unknown part of the component Conditional HTTP Request Handler. The manipulation of the argument ETags with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. CVE summarizes:

Applications that parse ETags from "If-Match" or "If-None-Match" request headers are vulnerable to DoS attack. Users of affected versions should upgrade to the corresponding fixed version. Users of older, unsupported versions could enforce a size limit on "If-Match" and "If-None-Match" headers, e.g. through a Filter.

The advisory is available at github.com. This vulnerability is traded as CVE-2024-38809 since 06/19/2024. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.

The vulnerability scanner Nessus provides a plugin with the ID 214601 (Oracle Business Intelligence Enterprise Edition (OAS 7.6) (January 2025 CPU)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.3.38, 6.0.23 or 6.1.12 eliminates this vulnerability. Applying the patch 8f33e3744084255bde0042dae69cd7dc957e7082 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (214601). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• Vmware

Name

• Spring Framework

Version

• 5.3.0
• 5.3.1
• 5.3.2
• 5.3.3
• 5.3.4
• 5.3.5
• 5.3.6
• 5.3.7
• 5.3.8
• 5.3.9
• 5.3.10
• 5.3.11
• 5.3.12
• 5.3.13
• 5.3.14
• 5.3.15
• 5.3.16
• 5.3.17
• 5.3.18
• 5.3.19
• 5.3.20
• 5.3.21
• 5.3.22
• 5.3.23
• 5.3.24
• 5.3.25
• 5.3.26
• 5.3.27
• 5.3.28
• 5.3.29
• 5.3.30
• 5.3.31
• 5.3.32
• 5.3.33
• 5.3.34
• 5.3.35
• 5.3.36
• 5.3.37
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.0.10
• 6.0.11
• 6.0.12
• 6.0.13
• 6.0.14
• 6.0.15
• 6.0.16
• 6.0.17
• 6.0.18
• 6.0.19
• 6.0.20
• 6.0.21
• 6.0.22
• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.1.4
• 6.1.5
• 6.1.6
• 6.1.7
• 6.1.8
• 6.1.9
• 6.1.10
• 6.1.11

License

• commercial

Website

• Vendor: https://www.vmware.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion