dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2024-38477

HIGH · 7.5 CVSS v3.1 Published 2024-07-01
Fix available
A fix is available. Upgrade to 2.4.60 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
null pointer dereference in mod_proxy in Apache HTTP Server 2.4.59 and earlier allows an attacker to crash the server via a malicious request. Users are recommended to upgrade to version 2.4.60, 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 · moderate confidence

A null pointer dereference vulnerability in mod_proxy in Apache HTTP Server 2.4.59 and earlier allows remote attackers to cause a denial of service by crashing the server through specially crafted malicious requests.

MitigationUpgrade Apache HTTP Server to version 2.4.60 or later to remediate this 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.60
Clustered Data OntapOperating system
Affected:= 9.0

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 version
    Run 'httpd -v' or 'apache2 -v' to display the server version. On some systems, check '/usr/sbin/httpd -v' or '/usr/sbin/apache2 -v'. For NetApp systems, use 'version' command in ONTAP CLI.
    Affected if Version is 2.4.59 or earlier (2.4.0 through 2.4.59 inclusive)
  2. Confirm mod_proxy module is loaded
    Check the loaded modules list by running 'httpd -M' or 'apache2ctl -M' and search for 'proxy_module' or 'mod_proxy' in the output. Alternatively, inspect the configuration files in /etc/httpd/conf.modules.d/ or /etc/apache2/mods-enabled/ for proxy-related LoadModule directives.
    Affected if mod_proxy module appears in the loaded modules list or is configured to load
  3. Verify proxy handlers are configured
    Review Apache configuration files (httpd.conf, proxy.conf, or included configuration files) for any ProxyPass, ProxyPassMatch, or ProxyRequests directives. Check for 'ProxyRequests On' settings which may enable proxy functionality.
    Affected if Any proxy-related directives (ProxyPass, ProxyPassReverse, or similar) are actively configured
  4. Check NetApp Clustered Data Ontap version if applicable
    If running NetApp storage systems, access the ONTAP CLI and run 'system node show -fields version' or 'version' to determine the exact ONTAP version.
    Affected if NetApp Clustered Data Ontap version is exactly 9.0

Environment is affected if Apache HTTP Server version is between 2.4.0 and 2.4.59 inclusive AND mod_proxy is loaded and configured, or if running NetApp Clustered Data Ontap version 9.0.

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.60 or later
Fixed in 2.4.60
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.60 or later to remediate this vulnerability.

Recommended fix High confidence

2.4.60

  1. 1. Back up your current Apache HTTP Server configuration and data directories
  2. 2. Stop the Apache HTTP Server service
  3. 3. Download Apache HTTP Server version 2.4.60 from the official Apache download site (httpd.apache.org)
  4. 4. Extract the new version and compile/install using standard build options matching your current configuration
  5. 5. Restore your configuration files from the backup
  6. 6. Start the Apache HTTP Server service
  7. 7. Verify the server is running and responding to requests correctly
  8. 8. Test that mod_proxy functionality is working as expected
Caveat Minor version upgrade within 2.4.x series; minimal configuration changes expected, but review mod_proxy settings for any deprecated directives

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

Fix this in HTTP Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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