dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2024-24795

MEDIUM · 6.3 CVSS v3.1 Published 2024-04-04
Fix available
A fix is available. Upgrade to 2.4.59 / 14.6 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. Users are recommended to upgrade to version 2.4.59, which fixes this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HTTP Response splitting vulnerability in Apache HTTP Server across multiple modules allows attackers to inject malicious response headers into backend applications, enabling HTTP desynchronization attacks that can manipulate client-server communications.

MitigationUpgrade Apache HTTP Server to version 2.4.59 or later to address the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HTTP ServerWeb server / proxy
Affected:>= 2.4.0, < 2.4.59
Debian LinuxOperating system
Affected:= 10.0
FedoraOperating system
Affected:= 38= 39= 40
OntapApplication
Affected:= 9
Ontap ToolsApplication
Affected:= 10
Fabric Operating SystemOperating system
Affected:all versions
macOSOperating system
Affected:< 14.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache HTTP Server installation
    Run 'httpd -v' or 'apache2 -v' to retrieve the installed version number
    Affected if The version displayed is 2.4.0 through 2.4.58 inclusive
  2. Check OS-packaged Apache version
    On Debian/Ubuntu: 'dpkg -l | grep apache2'; On Fedora/RHEL: 'rpm -qa | grep httpd'; On macOS: 'httpd -v' or check /usr/sbin/httpd
    Affected if The reported Apache version is 2.4.0 to 2.4.58, or the package version indicates a version prior to 2.4.59
  3. Verify NetApp environment
    For NetApp ONTAP 9 or ONTAP Tools 10, consult the product documentation or run 'system node version' to confirm the embedded Apache component version
    Affected if The product ships with a bundled Apache version prior to 2.4.59
  4. Confirm Broadcom Fabric OS
    Check the Fabric Operating System version via CLI: 'version' or through management interface
    Affected if Any version of Broadcom Fabric OS is running, as all versions are affected

You are affected if the Apache HTTP Server version in your environment is 2.4.0 or higher but lower than 2.4.59, or if you run any version of the listed affected products that bundle a vulnerable Apache version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.59 / 14.6 or later
Fixed in 2.4.5914.6
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.59 or later to address the vulnerability.

Recommended fix High confidence

2.4.59

  1. Identify the current Apache HTTP Server version using 'httpd -v' or 'apache2 -v'
  2. Stop the Apache service using 'systemctl stop httpd' or 'systemctl stop apache2'
  3. Update package repositories if using a package manager
  4. Install Apache HTTP Server version 2.4.59 using the appropriate package manager command (e.g., 'apt-get install apache2=2.4.59-*' for Debian/Ubuntu, 'yum update httpd' or 'dnf update httpd' for RHEL/Fedora)
  5. Alternatively, if compiled from source, download httpd-2.4.59 from apache.org, extract, and rebuild with './configure && make && make install'
  6. Verify the new version is installed using 'httpd -v' or 'apache2 -v'
  7. Restart the Apache service using 'systemctl start httpd' or 'systemctl start apache2'
  8. Verify the service is running properly and test web applications
Caveat Minor version upgrade within 2.4.x series typically does not introduce breaking changes; this is a security-focused release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24795 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data