Critical HTTP Response Splitting Vulnerability in Apache2 Package

apache2 Updated 03 Oct 2025

Summary

04/04/2024
N/A
No i
Medium
6.3

UBUNTU-CVE-2024-24795: HTTP Response splitting in multiple modules in Apache HTTP Server allows an attacker that can inject malicious response headers into backend applications to cause an HTTP desynchronization attack. Affects apache2 versions 2.4.6-2ubuntu2 – 2.4.7-1ubuntu4.9. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache2 is a widely-used open-source web server software that enables the hosting of websites and applications. It is known for its flexibility, power, and extensive module support, allowing users to customize their server environment. However, it is susceptible to various vulnerabilities, including the recent HTTP response splitting issue, which can lead to significant security risks if not addressed promptly.

Vulnerability Detail

The vulnerability, identified as CVE-2024-24795, arises from HTTP response splitting in multiple modules of the Apache HTTP Server. This flaw allows an attacker who can inject malicious response headers into backend applications to execute an HTTP desynchronization attack. Such attacks can lead to unauthorized access, data leakage, or even complete server compromise. The severity of this vulnerability is rated with a CVSS score of 6.3, indicating a medium level of risk that requires immediate attention.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can implement strict input validation on backend applications to prevent the injection of malicious headers. However, this is not a substitute for applying the necessary updates to the Apache2 package.

Conclusion

The HTTP response splitting vulnerability in the Apache2 package poses a significant risk to web applications. It is crucial for users to upgrade to the patched version to safeguard their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for apache2 →

Share this vulnerability

FAQ

CVE-2024-24795 is a vulnerability in the Apache HTTP Server that allows attackers to exploit HTTP response splitting, potentially leading to serious security breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply uploading your manifest file, such as package-lock.json, you can check for vulnerabilities without any installation.

The risks include unauthorized access to sensitive data, potential server compromise, and the ability to manipulate user sessions through HTTP desynchronization attacks.

Yes, a patch is available. Users should upgrade to Apache2 version 2.4.59 or later to mitigate this vulnerability.

If immediate upgrading is not possible, implement strict input validation on your backend applications as a temporary workaround until you can apply the patch.

Related vulnerabilities

Recent vulnerabilities recorded for apache2.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback