dbcve.org
JunosOperating system · Juniper

CVE-2017-2314

HIGH · 7.5 CVSS v3.1 Published 2017-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Receipt of a malformed BGP OPEN message may cause the routing protocol daemon (rpd) process to crash and restart. By continuously sending specially crafted BGP OPEN messages, an attacker can repeatedly crash the rpd process causing prolonged denial of service. No other Juniper Networks products or platforms are affected by this issue. Affected releases are Juniper Networks Junos OS 12.3 prior to 12.3R12-S4, 12.3R13, 12.3R3-S4; 12.3X48 prior to 12.3X48-D50; 13.3 prior to 13.3R4-S11, 13.3R10; 14.1 prior to 14.1R8-S3, 14.1R9; 14.1X53 prior to 14.1X53-D40; 14.1X55 prior to 14.1X55-D35; 14.2 prior to 14.2R4-S7, 14.2R6-S4, 14.2R7; 15.1 prior to 15.1F2-S11, 15.1F4-S1-J1, 15.1F5-S3, 15.1F6, 15.1R4; 15.1X49 prior to 15.1X49-D100; 15.1X53 prior to 15.1X53-D33, 15.1X53-D50.

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 malformed BGP OPEN message triggers a crash in the Junos OS routing protocol daemon (rpd). The vulnerability exists in BGP session initialization parsing, where specially crafted OPEN messages cause a denial of service through repeated process restarts.

MitigationUpgrade Junos OS to a fixed version (12.3R12-S4+, 13.3R10+, 14.1R9+, 14.1X53-D40+, 14.1X55-D35+, 14.2R7+, 15.1R4+, 15.1X49-D100+, 15.1X53-D50+). As interim mitigation, restrict BGP peer access via ACLs or firewall filters to trusted neighbors only.

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
JunosOperating system
Affected:= 12.3= 12.3x48= 14.1= 14.1x53= 14.2= 15.1= 13.3= 14.1x55= 15.1x49= 15.1x53

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
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 checks

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

  1. Identify Junos OS version
    Run 'show version' or 'show system information' command to obtain the installed Junos version
    Affected if The version matches any of these affected releases: 12.3, 12.3X48, 13.3, 14.1, 14.1X53, 14.1X55, 14.2, 15.1, 15.1X49, 15.1X53
  2. Verify BGP protocol is configured
    Run 'show configuration protocols bgp' to check if BGP is enabled in the configuration
    Affected if BGP is configured and present in the active configuration
  3. Confirm BGP peers are defined
    Run 'show bgp summary' to display configured BGP neighbors and their state
    Affected if One or more BGP peers are configured, making the system susceptible to malformed OPEN messages
  4. Check BGP peer access controls
    Review firewall filters or ACLs applied to BGP peer interfaces using 'show configuration firewall' or 'show configuration access-list'
    Affected if BGP peers are allowed from untrusted or any source addresses without restrictive access controls

The environment is affected if the Junos version matches the affected list, BGP is configured with active peers, and those peers are not restricted by firewall filters or ACLs to trusted sources only.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to a fixed version (12.3R12-S4+, 13.3R10+, 14.1R9+, 14.1X53-D40+, 14.1X55-D35+, 14.2R7+, 15.1R4+, 15.1X49-D100+, 15.1X53-D50+). As interim mitigation, restrict BGP peer access via ACLs or firewall filters to trusted neighbors only.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2314 — 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-2017-2314 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