dbcve.org
JunosOperating system · Juniper

CVE-2014-0613

HIGH · 7.1 CVSS v2.0 Published 2014-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/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
The XNM command processor in Juniper Junos 10.4 before 10.4R16, 11.4 before 11.4R10, 12.1R before 12.1R8-S2, 12.1X44 before 12.1X44-D30, 12.1X45 before 12.1X45-D20, 12.1X46 before 12.1X46-D10, 12.2 before 12.2R7, 12.3 before 12.3R5, 13.1 before 13.1R3-S1, 13.2 before 13.2R2-S2, and 13.3 before 13.3R1, when xnm-ssl or xnm-clear-text is enabled, allows remote attackers to cause a denial of service (memory consumption) via unspecified vectors.

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 denial of service vulnerability exists in the XNM (XML Network Management) command processor of Juniper Junos. When xnm-ssl or xnm-clear-text is enabled, remote attackers can send unspecified vectors causing excessive memory consumption, leading to system exhaustion and denial of service.

MitigationUpgrade Junos to one of the fixed versions (10.4R16, 11.4R10, 12.1R8-S2, 12.1X44-D30, 12.1X45-D20, 12.1X46-D10, 12.2R7, 12.3R5, 13.1R3-S1, 13.2R2-S2, or 13.3R1). If immediate upgrade is not feasible, disable xnm-ssl and xnm-clear-text services if not required for operations.

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:= 10.4= 11.4= 12.1r= 12.1x44= 12.1x45= 12.1x46= 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
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/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 Junos version
    Run 'show version' or 'show version detail' to obtain the installed Junos version
    Affected if The installed version matches one of the affected versions: 10.4, 11.4, 12.1r, 12.1x44, 12.1x45, 12.1x46, 12.2, 12.3, 13.1, 13.2, or 13.3
  2. Check xnm-ssl service status
    Run 'show configuration system services xnm-ssl' or check the configuration under 'set system services xnm-ssl'
    Affected if The xnm-ssl service is enabled in the configuration
  3. Check xnm-clear-text service status
    Run 'show configuration system services xnm-clear-text' or check the configuration under 'set system services xnm-clear-text'
    Affected if The xnm-clear-text service is enabled in the configuration

You are affected if your Junos version is one of the listed affected versions AND either xnm-ssl or xnm-clear-text services are enabled in your 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos to one of the fixed versions (10.4R16, 11.4R10, 12.1R8-S2, 12.1X44-D30, 12.1X45-D20, 12.1X46-D10, 12.2R7, 12.3R5, 13.1R3-S1, 13.2R2-S2, or 13.3R1). If immediate upgrade is not feasible, disable xnm-ssl and xnm-clear-text services if not required for operations.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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