dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2018-1301

MEDIUM · 5.9 CVSS v3.0 Published 2018-03-26
Fix available
A fix is available. Upgrade to after 2.4.29 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. This vulnerability is considered very hard if not impossible to trigger in non-debug mode (both log and build level), so it is classified as low risk for common server usage.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A specially crafted HTTP request with oversized headers can cause an out-of-bounds memory access in Apache HTTP Server versions prior to 2.4.30, potentially causing a denial of service. The vulnerability is extremely difficult to trigger outside of debug build and logging configurations.

MitigationUpgrade Apache HTTP Server to version 2.4.30 or later to remediate this vulnerability; given the difficulty of exploitation in normal production environments, this is a low-priority patch but should still be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HTTP ServerWeb server / proxy
Affected:<= 2.4.29
Debian LinuxOperating system
Affected:= 7.0= 8.0= 9.0
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 16.04= 17.10= 18.04
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 7.4= 7.5= 7.6
Santricity Cloud ConnectorApplication
Affected:all versions
Storage Automation StoreApplication
Affected:all versions
StoragegridApplication
Affected:all versions
Clustered Data OntapOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Apache HTTP Server version
    Run 'apache2 -v' on Debian/Ubuntu or 'httpd -v' on Red Hat/CentOS. Alternatively, check via package manager: 'dpkg -l | grep apache2' or 'rpm -qa | grep httpd'.
    Affected if The installed version is 2.4.29 or earlier.
  2. Confirm Apache is running and accessible
    Check if the Apache service is active with 'systemctl status apache2' (or 'httpd' on RHEL). Verify the service is listening on port 80/443 with 'netstat -tlnp | grep -E ':(80|443)' or 'ss -tlnp | grep -E ':(80|443)'.'
    Affected if Apache is running and accepting connections; the vulnerability only applies to running servers.
  3. Review debug and logging configuration
    Examine httpd.conf or apache2.conf for 'LogLevel debug' or oversized buffer/log settings. Check for any custom header logging modules enabled (mod_log_forensic, custom LogFormat directives capturing full headers).
    Affected if Debug logging (LogLevel debug) is enabled, which the CVE notes makes exploitation more feasible.
  4. Check for affected NetApp products
    If running NetApp products (Santricity Cloud Connector, Storage Automation Store, StorageGrid, Clustered Data Ontap), verify the underlying Apache version bundled with these products via 'netstat -ap | grep httpd' or product-specific diagnostics.
    Affected if Any NetApp product listed in affected versions is in use; these include all versions of the specified NetApp products.

You are affected if Apache HTTP Server version 2.4.29 or earlier is installed and running, particularly with debug logging enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2.4.29
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.30 or later to remediate this vulnerability; given the difficulty of exploitation in normal production environments, this is a low-priority patch but should still be applied.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1301 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data