dbcve.org
JunosOperating system · Juniper

CVE-2014-2713

MEDIUM · 5.0 CVSS v2.0 Published 2014-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 Junos before 11.4R11, 12.1 before 12.1R9, 12.2 before 12.2R7, 12.3R4 before 12.3R4-S3, 13.1 before 13.1R4, 13.2 before 13.2R2, and 13.3 before 13.3R1, as used in MX Series and T4000 routers, allows remote attackers to cause a denial of service (PFE restart) via a crafted IP packet to certain (1) Trio or (2) Cassis-based Packet Forwarding Engine (PFE) modules.

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 Junos before 11.4R11, 12.1R9, 12.2R7, 12.3R4-S3, 13.1R4, 13.2R2, and 13.3R1 on MX Series and T4000 routers contains a vulnerability in Trio and Cassis-based Packet Forwarding Engine (PFE) modules where processing a crafted IP packet triggers a PFE restart, causing denial of service.

MitigationUpgrade Junos to the specified patched versions (11.4R11, 12.1R9, 12.2R7, 12.3R4-S3, 13.1R4, 13.2R2, or 13.3R1 or later) on affected MX Series and T4000 routers to prevent crafted packet-based DoS attacks.

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:= 11.4= 12.1= 12.2= 12.3= 13.1= 13.2= 13.3

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
Partial

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

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 device model
    Run 'show chassis hardware' or check the physical router model to confirm it is an MX Series router or T4000 router
    Affected if Device is not an MX Series or T4000 router - these are the only affected platforms
  2. Check Junos version
    Run 'show version' to obtain the installed Junos version
    Affected if Version is 11.4, 12.1, 12.2, 12.3, 13.1, 13.2, or 13.3 and is below the patched releases (11.4R11, 12.1R9, 12.2R7, 12.3R4-S3, 13.1R4, 13.2R2, or 13.3R1)
  3. Verify PFE type
    Run 'show chassis fpc' or 'show pic fpc-slot' to identify the Packet Forwarding Engine type
    Affected if PFE is Trio or Cassis-based, as these are the specific implementations containing the vulnerability

The environment is affected if the device is an MX Series or T4000 router running a vulnerable Junos version (11.4 through 13.3 before the patched releases) with a Trio or Cassis-based PFE processing 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

Upgrade Junos to the specified patched versions (11.4R11, 12.1R9, 12.2R7, 12.3R4-S3, 13.1R4, 13.2R2, or 13.3R1 or later) on affected MX Series and T4000 routers to prevent crafted packet-based DoS attacks.

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-2014-2713 — 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-2713 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