Cyber Resilience

CVE-2024-38473

Apache Http Server 2.4.0 – 2.4.60

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

Summary

CVE-2024-38473 is a high-severity Improper Encoding or Escaping of Output (CWE-116) vulnerability in Apache Http Server. Its CVSS base score is 8.1 (High).

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

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-38473 is an encoding flaw in the mod_proxy module of Apache HTTP Server versions 2.4.59 and earlier. The defect allows specially crafted request URLs containing incorrect encoding to be forwarded to backend services, which can result in authentication bypass. The vulnerability is tracked under CWE-116 and carries a CVSS 3.1 score of 8.1.

An attacker with low privileges and network access can send malformed requests through the proxy. Successful exploitation may expose sensitive data from protected backends or disrupt service availability without requiring user interaction.

Apache recommends immediate upgrade to version 2.4.60. Corresponding advisories from the Apache project and NetApp detail the fixed release and urge administrators to apply the update to eliminate the encoding mishandling in mod_proxy. The associated EPSS score has remained at 0.8854 since disclosure.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Encoding problem in mod_proxy in Apache HTTP Server 2.4.59 and earlier allows request URLs with incorrect encoding to be sent to backend services, potentially bypassing authentication via crafted requests. Users are recommended to upgrade to version 2.4.60, which fixes this…

more

issue.

CWE(s)
CWE-116

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.
attack.mitre.org →
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.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38474Same product: Apache Http Server
CVE-2024-39573Same product: Apache Http Server
CVE-2024-38472Same product: Apache Http Server
CVE-2024-36387Same 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-27316Same product: Apache Http Server
CVE-2024-38477Same product: Apache Http Server
CVE-2024-38476Same product: Apache Http Server

Affected Assets

apache
http server
2.4.0 — 2.4.60
netapp
ontap
9

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.

SI-15 Information Output Filtering
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.

A.8.28 Secure coding mostly match
prevents

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

A.8.29 Security testing in development and acceptance mostly match
finds

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

A.8.25 Secure development life cycle partial match
prevents

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

A.8.26 Application security requirements partial match
prevents

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

A.8.27 Secure system architecture and engineering principles partial match
prevents

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

References