Apache2 - Race Condition and URL Normalization Vulnerabilities

apache2 Updated 02 Oct 2025

Summary

03/04/2019
N/A
Yes i
Unrated
Not published

DLA-1748-1: apache2 - security update. Affects apache2 versions < 2.4.10-10+deb8u14. Fixed in 2.4.10-10+deb8u14. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Apache2 is a widely used open-source web server software that provides a robust and secure platform for hosting websites. It offers various features and modules to handle HTTP requests, including authentication and URL rewriting. However, two vulnerabilities have been discovered in Apache2 that could potentially compromise its security.

Vulnerability Detail

The first vulnerability, identified as CVE-2019-0217, is a race condition in the mod_auth_digest module when running in a threaded server. This flaw allows a user with valid credentials to authenticate using another username, bypassing configured access control restrictions. The second vulnerability, CVE-2019-0220, involves inconsistent handling of URL normalizations. When the path component of a request URL contains multiple consecutive slashes ('/'), certain directives like LocationMatch and RewriteRule fail to account for duplicates in regular expressions, potentially leading to unintended consequences in the server's processing.

How To Fix

Minimum fixed version

2.4.10-10+deb8u14

This is the first release that contains the fix.

sudo apt-get install --only-upgrade apache2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

No specific workarounds have been mentioned for these vulnerabilities. Upgrading to the fixed version is the recommended solution.

Conclusion

The vulnerabilities in Apache2, namely CVE-2019-0217 and CVE-2019-0220, can potentially allow unauthorized access and cause inconsistencies in URL normalizations. It is crucial to upgrade to the fixed version to ensure the security and stability of your Apache2 server. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for apache2 →

Share this vulnerability

FAQ

CVE-2019-0217 allows an attacker with valid credentials to authenticate using another username, potentially bypassing access control restrictions. This could lead to unauthorized access to sensitive resources or information.

CVE-2019-0220 can cause inconsistencies in URL normalizations, particularly when the path component of a request URL contains multiple consecutive slashes ('/'). This can result in unexpected behavior in directives like LocationMatch and RewriteRule.

At the time of this report, there are no known public exploits targeting these vulnerabilities. However, it is crucial to apply the recommended updates to mitigate any potential risks.

Yes, both CVE-2019-0217 and CVE-2019-0220 can be exploited remotely if the affected Apache2 server is accessible over the network.

In addition to keeping the software up to date, it is advisable to regularly review and adjust access control configurations, implement strong authentication mechanisms, and monitor server logs for any suspicious activity.

Related vulnerabilities

Recent vulnerabilities recorded for apache2.

How To Fix

Minimum fixed version

2.4.10-10+deb8u14

This is the first release that contains the fix.

sudo apt-get install --only-upgrade apache2

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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