dbcve.org
JunosOperating system · Juniper

CVE-2017-2312

MEDIUM · 6.5 CVSS v3.0 Published 2017-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Juniper Networks devices running Junos OS affected versions and with LDP enabled, a specific LDP packet destined to the RE (Routing Engine) will consume a small amount of the memory allocated for the rpd (routing protocol daemon) process. Over time, repeatedly receiving this type of LDP packet(s) will cause the memory to exhaust and the rpd process to crash and restart. It is not possible to free up the memory that has been consumed without restarting the rpd process. This issue affects Junos OS based devices with either IPv4 or IPv6 LDP enabled via the [protocols ldp] configuration (the native IPv6 support for LDP is available in Junos OS 16.1 and higher). The interface on which the packet arrives needs to have LDP enabled. The affected Junos versions are: 13.3 prior to 13.3R10; 14.1 prior to 14.1R8; 14.2 prior to 14.2R7-S6 or 14.2R8; 15.1 prior to 15.1F2-S14, 15.1F6-S4, 15.1F7, 15.1R4-S7, 15.1R5; 15.1X49 before 15.1X49-D70; 15.1X53 before 15.1X53-D230, 15.1X53-D63, 15.1X53-D70; 16.1 before 16.1R2. 16.2R1 and all subsequent releases have a resolution for this vulnerability.

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 memory exhaustion vulnerability in Junos OS allows remote attackers to cause denial of service by sending specially crafted LDP packets to the Routing Engine. Each malicious packet consumes memory allocated to the rpd process without deallocation, eventually causing rpd to crash and restart.

MitigationIf LDP is not required, disable it via 'deactivate protocols ldp'. Otherwise, apply the vendor-provided patches for affected versions (13.3R10+, 14.1R8+, 14.2R7-S6/14.2R8+, etc.) or upgrade to 16.2R1+.

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:= 13.3= 14.1= 14.2= 15.1= 15.1x49= 15.1x53= 16.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 installed Junos version
    Run 'show version' or 'show system information' command and note the full version string
    Affected if Version matches 13.3, 14.1, 14.2, 15.1, 15.1x49, 15.1x53, or 16.1 series (e.g., 15.1R1, 15.1X49-D30, 16.1R1)
  2. Verify LDP protocol is enabled
    Run 'show protocols ldp' or 'show configuration protocols ldp' to check if LDP is configured and operational
    Affected if LDP protocol is enabled and operational on the device
  3. Check for recent rpd process crashes
    Run 'show system core-dumps' and review logs via 'show log messages' for rpd crash events, or use 'show system processes rpd' to check uptime
    Affected if rpd has recently crashed or restarted, especially correlating with LDP traffic
  4. Monitor LDP-related memory usage
    Use 'show system memory' and 'show system processes extensive' to observe rpd memory consumption, particularly if LDP is receiving traffic
    Affected if rpd memory usage is abnormally high or growing and LDP is actively receiving packets

Device is affected if it runs an affected Junos version (13.3-16.1 series), has LDP protocol enabled, and exhibits rpd memory exhaustion or crash events correlating with LDP traffic.

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

If LDP is not required, disable it via 'deactivate protocols ldp'. Otherwise, apply the vendor-provided patches for affected versions (13.3R10+, 14.1R8+, 14.2R7-S6/14.2R8+, etc.) or upgrade to 16.2R1+.

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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