Apache HTTP Server Vulnerability: Out of Bound Access in Apache2 Versions Prior to 2.4.33

apache2 Updated 02 Oct 2025

Summary

26/03/2018
N/A
Yes i
Medium
5.9

ALPINE-CVE-2018-1301: A specially crafted request could have crashed the Apache HTTP Server prior to version 2.4.30, due to an out of bound access after a size limit is reached by reading the HTTP header. Affects apache2 versions < 2.4.33-r0. Fixed in 2.4.33-r0. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Apache HTTP Server, commonly referred to as Apache, 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 features, making it a popular choice among developers and system administrators. However, certain versions of Apache2 are vulnerable to an out of bound access issue, which can lead to server crashes under specific conditions.

Vulnerability Detail

The vulnerability identified as CVE-2018-1301 allows a specially crafted request to crash the Apache HTTP Server prior to version 2.4.33. This issue arises from an out of bound access that occurs when the server reads the HTTP header and reaches a size limit. Although this vulnerability is considered low risk for common server usage, it poses a potential threat, especially in debug mode where it may be easier to trigger.

How To Fix

Minimum fixed version

2.4.33-r0

This is the first release that contains the fix.

sudo apk add --upgrade apache2

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

Workaround

As a workaround, consider disabling debug mode in your Apache configuration to minimize the risk of triggering this vulnerability. Additionally, ensure that your server is configured to handle requests securely and monitor logs for any unusual activity.

Conclusion

The Apache HTTP Server vulnerability CVE-2018-1301 presents a risk of server crashes due to out of bound access when handling HTTP requests. It is crucial to update to version 2.4.33 or later to mitigate this risk. Users should also consider workarounds and monitor their systems for any suspicious activity.

See every vulnerability recorded for apache2 →

Share this vulnerability

FAQ

CVE-2018-1301 is a vulnerability in the Apache HTTP Server that allows an attacker to crash the server through specially crafted requests.

Apache HTTP Server versions prior to 2.4.33 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 requiring any signup.

The CVSS score of this vulnerability is 5.9, indicating a moderate level of risk.

If immediate updating is not possible, consider disabling debug mode and monitoring your server for unusual activity as a temporary measure.

Related vulnerabilities

Recent vulnerabilities recorded for apache2.

How To Fix

Minimum fixed version

2.4.33-r0

This is the first release that contains the fix.

sudo apk add --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