CVE-2018-0027
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 · uneditedReceipt of a crafted or malformed RSVP PATH message may cause the routing protocol daemon (RPD) to hang or crash. When RPD is unavailable, routing updates cannot be processed which can lead to an extended network outage. If RSVP is not enabled on an interface, then the issue cannot be triggered via that interface. This issue only affects Juniper Networks Junos OS 16.1 versions prior to 16.1R3. This issue does not affect Junos releases prior to 16.1R1.
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 confidenceA malformed or crafted RSVP PATH message can cause the Juniper routing protocol daemon (RPD) to hang or crash. The vulnerability is triggerable only on interfaces where RSVP is explicitly enabled, and affects Junos OS 16.1 versions prior to 16.1R3. When RPD becomes unavailable, routing updates cannot be processed, potentially causing extended network outages.
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= 16.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Junos OS versionRun `show version` on the device and locate the Junos version in the output. Look for version string starting with 16.1Affected if Version shows 16.1 followed by any build prior to R3 (e.g., 16.1R1.x, 16.1R2.x, or 16.1 build before R3)
-
Verify RSVP protocol is enabledRun `show configuration protocols rsvp` or `show rsvp interface` to display RSVP configuration and active interfacesAffected if Any interface shows RSVP as enabled or listed in the RSVP interface output (this is required for the vulnerability to be triggerable)
-
Confirm RPD daemon statusRun `show system processes rpd` or check `show system processes extensive | match rpd` to verify the routing protocol daemon is runningAffected if RPD process is unstable, hung, or not running (indicating possible exploitation)
-
Review RSVP interface bindingsRun `show configuration interfaces <interface-name> unit <unit> family mpls` or examine interface MPLS configuration to identify which logical units have RSVP referencedAffected if RSVP is explicitly configured on any interface unit under MPLS family settings
The environment is affected if the device runs Junos 16.1 (any build prior to 16.1R3) AND has RSVP enabled on one or more interfaces, as the malformed RSVP PATH message can only trigger the crash when RSVP is explicitly configured.
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 dataUpgrade Junos OS to version 16.1R3 or later to patch the vulnerability. Alternatively, if RSVP is not required, disable RSVP on affected interfaces to eliminate the attack vector.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0027 — 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-0027 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