dbcve.org
JunosOperating system · Juniper

CVE-2017-2345

CRITICAL · 9.8 CVSS v3.0 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 →
100/100
Remediation priority · Urgent
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
On Junos OS devices with SNMP enabled, a network based attacker with unfiltered access to the RE can cause the Junos OS snmpd daemon to crash and restart by sending a crafted SNMP packet. Repeated crashes of the snmpd daemon can result in a partial denial of service condition. Additionally, it may be possible to craft a malicious SNMP packet in a way that can result in remote code execution. SNMP is disabled in Junos OS by default. Junos OS devices with SNMP disabled are not affected by this issue. No other Juniper Networks products or platforms are affected by this issue. NOTE: This is a different issue than Cisco CVE-2017-6736, CVE-2017-6737, and CVE-2017-6738. Affected releases are Juniper Networks Junos OS 12.1X46 prior to 12.1X46-D67; 12.3X48 prior to 12.3X48-D51, 12.3X48-D55; 13.3 prior to 13.3R10-S2; 14.1 prior to 14.1R2-S10, 14.1R8-S4, 14.1R9; 14.1X50 prior to 14.1X50-D185; 14.1X53 prior to 14.1X53-D122, 14.1X53-D44, 14.1X53-D50; 14.2 prior to 14.2R4-S9, 14.2R7-S7, 14.2R8; 15.1 prior to 15.1F2-S18, 15.1F6-S7, 15.1R4-S8, 15.1R5-S5, 15.1R6-S1, 15.1R7; 15.1X49 prior to 15.1X49-D100, 15.1X49-D110; 15.1X53 prior to 15.1X53-D231, 15.1X53-D47, 15.1X53-D48, 15.1X53-D57, 15.1X53-D64, 15.1X53-D70; 16.1 prior to 16.1R3-S4, 16.1R4-S3, 16.1R4-S4, 16.1R5; 16.2 prior to 16.2R2, 16.2R3; 17.1 prior to 17.1R1-S3, 17.1R2, 17.1R3; 17.2 prior to 17.2R1-S1, 17.2R2; 17.2X75 prior to 17.2X75-D30. Junos releases prior to 10.2 are not affected.

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 vulnerability in the Junos OS snmpd daemon allows a network-based attacker with unfiltered access to the Routing Engine to send crafted SNMP packets causing the daemon to crash and restart. Repeated crashes create a partial denial of service, and certain crafted packets may enable remote code execution. SNMP must be enabled for exploitation.

MitigationEnable SNMP only when necessary, restrict access to the Routing Engine via firewall policies/ACLs, and upgrade to the specified Junos OS version corresponding to the release branch.

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.1x46= 12.3x48= 13.3= 14.1= 14.1x50= 14.1x53= 14.2= 15.1= 15.1x49= 15.1x53= 16.1= 16.2

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the Junos OS version
    Run 'show version' or 'show version detail' to obtain the installed Junos OS version
    Affected if The installed version matches one of these: 12.1x46, 12.3x48, 13.3, 14.1, 14.1x50, 14.1x53, 14.2, 15.1, 15.1x49, 15.1x53, 16.1, or 16.2
  2. Determine if SNMP is enabled
    Run 'show snmp status' or inspect the configuration with 'show configuration | display set | match snmp'
    Affected if SNMP is enabled and configured on the device (the snmpd daemon is running)
  3. Verify SNMP service accessibility
    Check if UDP port 161 (SNMP) is open and reachable from untrusted networks using 'show services accounting status' or reviewing firewall policies
    Affected if SNMP service is accessible from network segments that are not trusted or filtered (especially the Routing Engine management interface)
  4. Review SNMP community string configuration
    Run 'show configuration snmp' to review community strings and trap configuration
    Affected if SNMP community strings are set (even default ones) and the service is reachable from an attacker's network location

A device is affected if it runs an affected Junos version (12.1x46 through 16.2), has SNMP enabled, and the SNMP service is accessible to an untrusted network attacker who can reach the Routing Engine.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable SNMP only when necessary, restrict access to the Routing Engine via firewall policies/ACLs, and upgrade to the specified Junos OS version corresponding to the release branch.

Recommended fix High confidence

Upgrade to the fixed version for your release branch: 12.1X46-D67 or later; 12.3X48-D51/D55 or later; 13.3R10-S2 or later; 14.1R2-S10, 14.1R8-S4, 14.1R9 or later; 14.1X50-D185 or later; 14.1X53-D122/D44/D50 or later; 14.2R4-S9, 14.2R7-S7, 14.2R8 or later; 15.1F2-S18, 15.1F6-S7, 15.1R4-S8, 15.1R5-S5,

  1. 1. Verify SNMP is enabled on the device: run 'show snmp statistics' or check configuration with 'show configuration | display set | grep snmp'
  2. 2. If SNMP is disabled, no action is required - the device is not affected by this vulnerability
  3. 3. If SNMP is enabled, identify the current Junos OS version with 'show version'
  4. 4. Determine the appropriate fixed version for your current release branch from the affected versions list
  5. 5. Plan and schedule a maintenance window for the upgrade
  6. 6. Download the appropriate Junos OS service release from the Juniper Networks support portal (kb.juniper.net)
  7. 7. Upload the Junos OS upgrade package to the device
  8. 8. Install the upgrade using 'request system software add <package-name>'
Caveat Standard Junos upgrade precautions apply - ensure configuration backup, check hardware compatibility, and plan for possible rollback if issues arise

Generated from the published advisory — verify against the referenced sources before acting.

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