Cyber Resilience

CVE-2024-38474

Apache Http Server 2.4.0 – 2.4.60

Published
01 July 2024
Modified
25 March 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.025 83th percentile
Risk Priority 76 floored blend · peak EPSS

Summary

CVE-2024-38474 is a critical-severity Improper Encoding or Escaping of Output (CWE-116) vulnerability in Apache Http Server. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 17% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Substitution encoding issue in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows attacker to execute scripts in directories permitted by the configuration but not directly reachable by any URL or source disclosure of scripts meant to only to be…

more

executed as CGI. Users are recommended to upgrade to version 2.4.60, which fixes this issue. Some RewriteRules that capture and substitute unsafely will now fail unless rewrite flag "UnsafeAllow3F" is specified.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38473Same product: Apache Http Server
CVE-2024-38477Same product: Apache Http Server
CVE-2024-38476Same product: Apache Http Server
CVE-2024-38475Same product: Apache Http Server
CVE-2023-28486Same product class: NAS / storage appliance
CVE-2023-28487Same product class: NAS / storage appliance
CVE-2024-39573Same product: Apache Http Server
CVE-2024-38472Same product: Apache Http Server
CVE-2024-39884Same product: Apache Http Server
CVE-2024-36387Same product: Apache Http Server

Affected Assets

apache
http server
2.4.0 — 2.4.60
netapp
clustered data ontap
9.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.2.1
  • V1.2.3

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-116

Validating that output matches expected content directly mitigates failures to properly encode or escape data for its destination context.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper output encoding to prevent injection and message malformation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.

finds

Security testing can detect missing or incorrect encoding but does not itself implement the control.

prevents

Secure development life cycle mandates output encoding/escaping practices that directly prevent improper encoding.

prevents

Application security requirements include explicit rules for safe output handling and encoding.

prevents

Secure architecture principles reduce the likelihood of missing encoding but do not prescribe the actual technique.

References