dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2024-39884

MEDIUM · 6.2 CVSS v3.1 Published 2024-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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
A regression in the core of Apache HTTP Server 2.4.60 ignores some use of the legacy content-type based configuration of handlers.   "AddType" and similar configuration, under some circumstances where files are requested indirectly, result in source code disclosure of local content. For example, PHP scripts may be served instead of interpreted. Users are recommended to upgrade to version 2.4.61, 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 regression in Apache HTTP Server 2.4.60 causes the server to ignore certain legacy content-type based handler configurations (like AddType). When files are requested indirectly, this can cause PHP scripts and other source files to be served as plain text rather than being interpreted/executed, resulting in source code disclosure.

MitigationUpgrade Apache HTTP Server to version 2.4.61, which contains the fix for this regression.

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.60
Ontap ToolsApplication
Affected:= 10

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

CVSS:3.1/AV:L/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' to display the server version, or check the ServerTokens/ServerVersion directive in the configuration.
    Affected if The version displayed is exactly 2.4.60
  2. Identify legacy content-type handlers
    Search configuration files (httpd.conf, .htaccess) for 'AddType', 'AddHandler', or similar directives that map file extensions to content types or handlers (e.g., AddType application/x-httpd-php .php).
    Affected if Any AddType or AddHandler directives exist that map PHP or other executable file types to handlers.
  3. Verify PHP script handling via indirect requests
    Place a test PHP file in a directory served by Apache and request it indirectly (e.g., via directory index or rewrite rule) rather than directly requesting the file by name. Observe whether the PHP source code is displayed as plain text.
    Affected if PHP source code is displayed in the browser instead of being executed.
  4. Check NetApp ONTAP Tools version if applicable
    If NetApp ONTAP Tools version 10 is deployed, check the embedded Apache version using 'about' or system diagnostics within the ONTAP Tools interface.
    Affected if ONTAP Tools version 10 is running with embedded Apache 2.4.60.

You are affected if Apache HTTP Server version is exactly 2.4.60 and you use legacy content-type handlers (AddType/AddHandler) that are now being ignored, resulting in source code being served as plain text.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache HTTP Server to version 2.4.61, which contains the fix for this regression.

Recommended fix High confidence

Apache HTTP Server 2.4.61

  1. 1. Identify the Apache HTTP Server installation method (package manager, source compilation, or vendor-specific)
  2. 2. For package-managed systems (yum/apt): Check for available updates using 'yum check-update httpd' or 'apt-get update && apt-get upgrade apache2'
  3. 3. For source installations: Download Apache HTTP Server 2.4.61 from https://httpd.apache.org/download.cgi
  4. 4. For NetApp Ontap Tools: Consult the NetApp security advisory at security.netapp.com for product-specific upgrade instructions
  5. 5. After upgrading, restart the Apache HTTP Server to load the new version
  6. 6. Verify the installed version using 'httpd -v' or 'apache2 -v' to confirm version 2.4.61 is running
  7. 7. Test that AddType configurations work correctly for the intended handler behavior
Caveat Review Apache HTTP Server 2.4.61 release notes at httpd.apache.org for any behavioral changes or deprecations

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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