CVE-2018-0050
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 · uneditedAn error handling vulnerability in Routing Protocols Daemon (RPD) of Juniper Networks Junos OS allows an attacker to cause RPD to crash. Continued receipt of this malformed MPLS RSVP packet will cause a sustained Denial of Service condition. Affected releases are Juniper Networks Junos OS: 14.1 versions prior to 14.1R8-S5, 14.1R9; 14.1X53 versions prior to 14.1X53-D48 on QFX Switching; 14.2 versions prior to 14.1X53-D130 on QFabric System; 14.2 versions prior to 14.2R4. This issue does not affect versions of Junos OS before 14.1R1. Junos OS RSVP only supports IPv4. IPv6 is not affected by this issue. This issue require it to be received on an interface configured to receive this type of traffic.
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 confidenceAn error handling vulnerability in the Routing Protocols Daemon (RPD) of Juniper Networks Junos OS allows an attacker to cause RPD to crash by sending malformed MPLS RSVP packets. Continued receipt of these packets results in a sustained Denial of Service. The attack requires the packet to be received on an interface configured to process this type of traffic, and only affects IPv4 (IPv6 is not impacted).
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= 14.1= 14.1x53= 14.2CVSS 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 the command 'show version' or 'show version detail' to display the installed Junos OS versionAffected if The version displayed matches 14.1, 14.1x53, or 14.2 series (including all subversions before the fixed releases)
-
Verify RSVP protocol is configuredRun 'show configuration protocols rsvp' to check if RSVP is enabled in the Junos configurationAffected if RSVP is present in the configuration and actively enabled
-
Confirm MPLS is enabled with RSVP signalingRun 'show configuration protocols mpls' to check if MPLS is configured, as RSVP is typically used for MPLS traffic engineeringAffected if MPLS is configured and RSVP is used as the signaling protocol
-
Identify RSVP-enabled interfacesRun 'show rsvp interface' to list all interfaces where RSVP is enabled and activeAffected if Any interface is listed as RSVP-enabled and capable of receiving MPLS RSVP packets
-
Check interface access exposureReview interface configurations with 'show configuration interfaces' to determine if RSVP-enabled interfaces are directly exposed to untrusted networksAffected if RSVP-enabled interfaces are reachable from untrusted network segments
You are affected if your Junos device runs version 14.1, 14.1x53, or 14.2 AND has RSVP/MPLS enabled on interfaces that can receive packets from untrusted sources.
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 the fixed versions (14.1R8-S5 and later, 14.1X53-D48 or later for QFX, 14.1X53-D130 or later for QFabric, 14.2R4 or later). Until upgrade is possible, restrict RSVP traffic to trusted interfaces only.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0050 — 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-0050 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