dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2018-1302

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
When an HTTP/2 stream was destroyed after being handled, the Apache HTTP Server prior to version 2.4.30 could have written a NULL pointer potentially to an already freed memory. The memory pools maintained by the server make this vulnerability hard to trigger in usual configurations, the reporter and the team could not reproduce it outside debug builds, so it is classified as low risk.

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 · moderate confidence

In Apache HTTP Server versions prior to 2.4.30, when an HTTP/2 stream was destroyed after being handled, the server could write a NULL pointer to already freed memory. This NULL pointer dereference occurs due to improper memory pool handling during HTTP/2 stream destruction.

MitigationUpgrade to Apache HTTP Server version 2.4.30 or later. Given the difficulty of exploitation (not reproducible outside debug builds in normal configurations), prioritize upgrading production servers during regular maintenance windows.

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
Ubuntu LinuxOperating system
Affected:= 18.04
Clustered Data OntapApplication
Affected:all versions
Santricity Cloud ConnectorApplication
Affected:all versions
Storage Automation StoreApplication
Affected:all versions
StoragegridApplication
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 Apache HTTP Server version
    Run `apache2 -v` (Debian/Ubuntu) or `httpd -v` (Red Hat/CentOS) to obtain the installed server version number.
    Affected if The installed version is 2.4.29 or lower.
  2. Confirm HTTP/2 module is loaded
    Run `apache2ctl -M` (Debian/Ubuntu) or `httpd -M` (Red Hat/CentOS) and search for 'http2_module' in the module list.
    Affected if The http2_module appears in the loaded modules list.
  3. Verify HTTP/2 protocol is enabled
    Inspect Apache configuration files (typically in /etc/apache2 or /etc/httpd/conf.d/) for 'Protocols h2 h2c' or 'Protocols h2' directives.
    Affected if The configuration contains HTTP/2 protocol directives, enabling HTTP/2 connections.
  4. Check NetApp product families (if applicable)
    For NetApp systems (Clustered Data ONTAP, Santricity Cloud Connector, Storage Automation Store, StorageGrid), consult the vendor advisory for specific version detection methods.
    Affected if The system runs any affected NetApp product listed in the CVE.

A system is affected if it runs Apache HTTP Server 2.4.29 or earlier WITH the HTTP/2 module loaded AND HTTP/2 protocol enabled in configuration, or runs any version of the affected NetApp products.

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 to Apache HTTP Server version 2.4.30 or later. Given the difficulty of exploitation (not reproducible outside debug builds in normal configurations), prioritize upgrading production servers during regular maintenance windows.

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-1302 — 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-1302 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