HTTP Response Splitting Affecting log4j-slf4j package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL9-LOG4JSLF4J-10350296
- published13 Jun 2025
- disclosed12 Jun 2025
Introduced: 12 Jun 2025
NewCVE-2025-41234 (opens in a new tab)How to fix?
There is no fixed version for RHEL:9 log4j-slf4j.
NVD Description
Note: Versions mentioned in the description apply only to the upstream log4j-slf4j package and not the log4j-slf4j package as distributed by RHEL.
See How to fix? for RHEL:9 relevant fixed versions and status.
Description
In Spring Framework, versions 6.0.x as of 6.0.5, versions 6.1.x and 6.2.x, an application is vulnerable to a reflected file download (RFD) attack when it sets a “Content-Disposition” header with a non-ASCII charset, where the filename attribute is derived from user-supplied input.
Specifically, an application is vulnerable when all the following are true:
- The header is prepared with org.springframework.http.ContentDisposition.
- The filename is set via ContentDisposition.Builder#filename(String, Charset).
- The value for the filename is derived from user-supplied input.
- The application does not sanitize the user-supplied input.
- The downloaded content of the response is injected with malicious commands by the attacker (see RFD paper reference for details).
An application is not vulnerable if any of the following is true:
The application does not set a “Content-Disposition” response header.
The header is not prepared with org.springframework.http.ContentDisposition.
The filename is set via one of: * ContentDisposition.Builder#filename(String), or
ContentDisposition.Builder#filename(String, ASCII)
The filename is not derived from user-supplied input.
The filename is derived from user-supplied input but sanitized by the application.
The attacker cannot inject malicious content in the downloaded content of the response.
Affected Spring Products and VersionsSpring Framework:
- 6.2.0 - 6.2.7
- 6.1.0 - 6.1.20
- 6.0.5 - 6.0.28
- Older, unsupported versions are not affected
MitigationUsers of affected versions should upgrade to the corresponding fixed version.
Affected version(s)Fix versionAvailability6.2.x6.2.8OSS6.1.x6.1.21OSS6.0.x6.0.29 Commercial https://enterprise.spring.io/ No further mitigation steps are necessary.
CWE-113 in Content-Disposition handling in VMware Spring Framework versions 6.0.5 to 6.2.7 allows remote attackers to launch Reflected File Download (RFD) attacks via unsanitized user input in ContentDisposition.Builder#filename(String, Charset) with non-ASCII charsets.