Critical Encoding Vulnerability in Apache2 Package: CVE-2024-38473

apache2 Updated 03 Oct 2025

Summary

01/07/2024
N/A
No i
High
8.1

UBUNTU-CVE-2024-38473: 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. Affects apache2 versions 2.4.6-2ubuntu2 – 2.4.7-1ubuntu4.9. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache2 is a widely used open-source web server software that enables the hosting of websites and web applications. It is known for its flexibility, power, and extensive support for various modules and configurations. However, it has recently been identified that versions prior to 2.4.60 are vulnerable to an encoding issue in mod_proxy, which can lead to serious security risks.

Vulnerability Detail

The vulnerability, identified as CVE-2024-38473, arises from an encoding problem in the mod_proxy module of Apache HTTP Server versions 2.4.59 and earlier. This flaw allows request URLs with incorrect encoding to be sent to backend services, potentially bypassing authentication mechanisms through crafted requests. The ramifications of this vulnerability are significant, as it could allow unauthorized access to sensitive data or services, leading to data breaches or service disruptions.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can implement strict input validation on the backend services to reject improperly encoded URLs. However, this is not a substitute for upgrading the affected software.

Conclusion

The CVE-2024-38473 vulnerability poses a significant risk to Apache2 users, allowing potential unauthorized access through crafted requests. It is essential to upgrade to version 2.4.60 or later to protect against this vulnerability. Users are encouraged to stay informed and utilize tools like Vulert for real-time monitoring of open-source vulnerabilities.

See every vulnerability recorded for apache2 →

Share this vulnerability

FAQ

CVE-2024-38473 is a critical vulnerability in the Apache2 web server that allows unauthorized access due to an encoding issue in mod_proxy.

Apache2 versions 2.4.59 and earlier are affected by this vulnerability.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The CVSS score of CVE-2024-38473 is 8.1, indicating a high severity level.

If an immediate upgrade is not possible, implement strict input validation on your backend services to mitigate the risk temporarily.

Related vulnerabilities

Recent vulnerabilities recorded for apache2.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback