dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2024-40898

HIGH · 7.5 CVSS v3.1 Published 2024-07-18
Fix available
A fix is available. Upgrade to 2.4.62 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
SSRF in Apache HTTP Server on Windows with mod_rewrite in server/vhost context, allows to potentially leak NTML hashes to a malicious server via SSRF and malicious requests. Users are recommended to upgrade to version 2.4.62 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

Apache HTTP Server mod_rewrite module in server/virtual host context on Windows contains an SSRF vulnerability that allows attackers to make the server perform requests to arbitrary URLs. This can be exploited to leak NTLM hashes to malicious servers via crafted requests through the vulnerable server.

MitigationUpgrade Apache HTTP Server to version 2.4.62 or later. This is the primary remediation as no workaround is mentioned; organizations should test the upgrade thoroughly, especially custom mod_rewrite configurations.

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.62

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

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

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') from the Apache bin directory to obtain the installed version number
    Affected if The installed version is lower than 2.4.62
  2. Confirm operating system is Windows
    Verify the Apache server is running on a Windows host (check OS via 'systeminfo' or 'ver' command)
    Affected if The Apache server is running on Windows - this vulnerability only applies on Windows
  3. Verify mod_rewrite module is loaded
    Check the Apache configuration (httpd.conf or included files) for 'LoadModule rewrite_module modules/mod_rewrite.so' or run 'httpd -M' to list loaded modules
    Affected if mod_rewrite is loaded/enabled in the configuration
  4. Inspect virtual host configurations for RewriteRule directives
    Search all httpd.conf, included config files, and virtual host definitions for 'RewriteRule' directives, particularly those using the '[P]' (proxy) flag or allowing arbitrary URL schemes
    Affected if RewriteRule directives exist in virtual host context that could be exploited for SSRF (especially with proxy flags or flexible patterns)

A user is affected if they run Apache HTTP Server on Windows with mod_rewrite enabled and a version lower than 2.4.62 that has exploitable RewriteRule configurations in virtual host context.

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.62 or later
Fixed in 2.4.62
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.62 or later. This is the primary remediation as no workaround is mentioned; organizations should test the upgrade thoroughly, especially custom mod_rewrite configurations.

Recommended fix High confidence

2.4.62

  1. 1. Back up the current Apache HTTP Server configuration files (httpd.conf, any included .conf files) and modules directory
  2. 2. Download Apache HTTP Server version 2.4.62 from the official Apache download site (https://httpd.apache.org/download.cgi)
  3. 3. Stop the Apache HTTP Server service
  4. 4. Install the new version of Apache HTTP Server 2.4.62, preserving custom configurations where prompted
  5. 5. Verify that mod_rewrite module is loaded in the configuration (LoadModule rewrite_module modules/mod_rewrite.so)
  6. 6. Restart the Apache HTTP Server service
  7. 7. Test that the server responds correctly and the mod_rewrite functionality works as expected

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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