dbcve.org
Junos EOperating system · Juniper

CVE-2014-6377

HIGH · 7.8 CVSS v2.0 Published 2014-10-14
Fix available
A fix is available. Upgrade to after 13.3.2 or later.
See remediation →
87/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
Juniper JunosE before 13.3.3p0-1, 14.x before 14.3.2, and 15.x before 15.1.0, when DEBUG severity icmpTraffic logging is enabled, allows remote attackers to cause a denial of service (SRP reset) via a crafted ICMP packet to the (1) interface or (2) loopback IP address, which triggers a processor exception in ip_RxData_8.

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

Juniper JunosE contains a denial-of-service vulnerability where enabling DEBUG severity icmpTraffic logging causes the device to crash when receiving crafted ICMP packets to the interface or loopback IP address. The packets trigger a processor exception in the ip_RxData_8 function, resulting in an SRP reset.

MitigationDisable DEBUG severity icmpTraffic logging in the configuration, or upgrade to JunosE version 13.3.3p0-1, 14.3.2, 15.1.0 or later to resolve the vulnerability.

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
Junos EOperating system
Affected:<= 13.3.2= 13.3.0= 13.3.1= 14.3.0= 14.3.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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/A:C

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. Check JunosE version
    Execute the command 'show version' or 'show system information' to retrieve the installed JunosE software version
    Affected if The version matches 13.3.0, 13.3.1, 13.3.2, 14.3.0, or 14.3.1 (or any version <=13.3.2)
  2. Verify icmpTraffic logging is enabled
    Run 'show configuration | find icmpTraffic' or 'show logging configuration' to check if icmpTraffic logging is configured on the device
    Affected if icmpTraffic logging is present in the active configuration
  3. Confirm DEBUG severity for icmpTraffic
    Examine the logging severity level setting for icmpTraffic, typically found under system logging or debug configuration options
    Affected if The severity level is set to DEBUG for icmpTraffic logging

The device is affected if it runs JunosE version 13.3.0 through 14.3.1 AND has DEBUG severity icmpTraffic logging enabled in the configuration

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
Upgrade available Upgrade to a release after 13.3.2
Interim mitigation

Disable DEBUG severity icmpTraffic logging in the configuration, or upgrade to JunosE version 13.3.3p0-1, 14.3.2, 15.1.0 or later to resolve the vulnerability.

Fix this in Junos E Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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