Node.jsApplication
CVE-2018-1000168
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 · uneditednghttp2 version >= 1.10.0 and nghttp2 <= v1.31.0 contains an Improper Input Validation CWE-20 vulnerability in ALTSVC frame handling that can result in segmentation fault leading to denial of service. This attack appears to be exploitable via network client. This vulnerability appears to have been fixed in >= 1.31.1.
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 confidencenghttp2 versions 1.10.0 through 1.31.0 contain improper input validation in ALTSVC frame handling. A specially crafted ALTSVC frame can trigger a segmentation fault, causing denial of service. The vulnerability is exploitable remotely via network interaction.
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
Node.jsApplication
>= 6.0.0, <= 6.8.1>= 8.4.0, <= 8.17.0>= 9.0.0, <= 9.11.2>= 10.0.0, < 10.4.1
Debian LinuxOperating system
= 9.0>= 1.10.0, <= 1.31.0CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify nghttp2 library versionRun 'nghttpd --version' or check the library file version using 'dpkg -l libnghttp2-*' on Debian, or inspect the shared library with 'ldd <binary> | grep nghttp2' or 'strings <lib> | grep nghttp2'Affected if The installed version falls within 1.10.0 through 1.31.0 inclusive
-
Check Node.js versionRun 'node --version' to identify the installed Node.js versionAffected if Node.js version is 6.0.0-6.8.1, 8.4.0-8.17.0, 9.0.0-9.11.2, or 10.0.0-10.4.0 (these versions bundle a vulnerable nghttp2)
-
Verify if ALTSVC frame handling is in useInspect network traffic or application logs for ALTSVC frame processing. Check application configuration for HTTP/2 alt-svc headers or ALTSVC enablement. Use 'nghttp -v <url>' to debug HTTP/2 frames if availableAffected if The application or service negotiates HTTP/2 ALTSVC frames - this feature must be enabled for the vulnerability to be reachable
-
Check Debian package versionRun 'apt-cache policy libnghttp2-14' or 'dpkg -l libnghttp2-14' on Debian 9 systemsAffected if The installed libnghttp2-14 package version is 1.10.0-1.31.0 inclusive
You are affected if nghttp2 library version 1.10.0-1.31.0 is installed AND ALTSVC frame handling is enabled or negotiated in your HTTP/2 communication.
Generated from the published advisory. Verify against your own configuration.
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 data10.4.1
Upgrade nghttp2 to version 1.31.1 or later. If upgrade is not immediately possible, consider network-level filtering of ALTSVC frames until the library can be updated.
Fix this in Node.js
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000168 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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