dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2024-36387

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-01
Fix available
A fix is available. Upgrade to after 2.4.59 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Serving WebSocket protocol upgrades over a HTTP/2 connection could result in a Null Pointer dereference, leading to a crash of the server process, degrading performance.

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 · moderate confidence

When WebSocket protocol upgrades are served over HTTP/2 connections, the server attempts to process the upgrade request but encounters a null pointer dereference due to improper handling of the HTTP/2 stream state for upgrade headers, causing the server process to crash.

MitigationDisable WebSocket upgrades over HTTP/2 connections or apply vendor-provided patches. Use HTTP/1.1 for WebSocket connections as a workaround until a fix is available.

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.55, <= 2.4.59
OntapApplication
Affected:= 9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Check Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to get the server version number
    Affected if Version is 2.4.55 through 2.4.59 inclusive
  2. Check if HTTP/2 is enabled
    Review the server configuration files (httpd.conf, ssl.conf) for 'Protocols h2 h2c http/1.1' or 'SSLProtocol' directives, or check if mod_http2 is loaded via 'httpd -M' | grep http2
    Affected if HTTP/2 protocol module (mod_http2) is loaded and enabled
  3. Check for WebSocket upgrade configurations
    Search config files for 'Upgrade' and 'WebSocket' directives, or review .htaccess files and VirtualHost configurations for upgrade headers
    Affected if WebSocket upgrade handling is configured on the server
  4. Identify active HTTP/2 connections handling upgrades
    Review server logs for any crash events or connection drops related to upgrade requests, and monitor active connections using server status page if available
    Affected if HTTP/2 connections are actively processing upgrade requests
  5. Confirm NetApp Ontap version (if applicable)
    For NetApp systems, run 'version' or check System Manager for the Ontap version
    Affected if NetApp Ontap version 9 is running

You are affected if you are running Apache HTTP Server 2.4.55-2.4.59 or NetApp Ontap 9, with HTTP/2 enabled and WebSocket upgrade requests being processed over HTTP/2 connections.

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 a release after 2.4.59
Interim mitigation

Disable WebSocket upgrades over HTTP/2 connections or apply vendor-provided patches. Use HTTP/1.1 for WebSocket connections as a workaround until a fix is available.

Recommended fix High confidence

Apache HTTP Server 2.4.60 or later

  1. 1. Identify all Apache HTTP Server instances running versions 2.4.55 through 2.4.59 in your environment
  2. 2. For each affected instance, plan a maintenance window to perform the upgrade
  3. 3. Download Apache HTTP Server version 2.4.60 or later from the official Apache website (httpd.apache.org) or your Linux distribution's package repository
  4. 4. Before upgrading, back up your current Apache configuration files (httpd.conf, any included conf files)
  5. 5. Stop the Apache HTTP Server service gracefully
  6. 6. Install the upgraded Apache HTTP Server package or compile from source
  7. 7. Verify the configuration syntax is valid: 'httpd -t' or 'apachectl configtest'
  8. 8. Start the Apache HTTP Server service
Caveat Minor: Review the Apache HTTP Server 2.4.60 release notes for any configuration or module changes that may affect your deployment

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

Fix this in HTTP Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36387 — 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-36387 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