dbcve.org
JunosOperating system · Juniper

CVE-2013-6014

CRITICAL · 9.3 CVSS v3.1 Published 2013-10-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
98/100
Remediation priority · Urgent
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 10.4 before 10.4S15, 11.4 before 11.4R9, 11.4X27 before 11.4X27.44, 12.1 before 12.1R7, 12.1X44 before 12.1X44-D20, 12.1X45 before 12.1X45-D15, 12.2 before 12.2R6, 12.3 before 12.3R3, 13.1 before 13.1R3, and 13.2 before 13.2R1, when Proxy ARP is enabled on an unnumbered interface, allows remote attackers to perform ARP poisoning attacks and possibly obtain sensitive information via a crafted ARP message.

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 contains a vulnerability where Proxy ARP enabled on an unnumbered interface fails to properly validate ARP messages, allowing remote attackers to send crafted ARP messages and perform ARP poisoning attacks. This can enable man-in-the-middle attacks and disclosure of sensitive information.

MitigationUpgrade Junos to the fixed versions (10.4S15, 11.4R9, 11.4X27.44, 12.1R7, 12.1X44-D20, 12.1X45-D15, 12.2R6, 12.3R3, 13.1R3, 13.2R1 or later). Alternatively, if Proxy ARP is not required, disable it on unnumbered interfaces.

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= 11.4x27= 12.1= 12.1x44= 12.1x45= 12.2= 12.3= 13.1= 13.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/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 Junos version
    Run 'show version' or 'show version detail' on the Juniper device
    Affected if Version matches 10.4, 11.4, 11.4x27, 12.1, 12.1x44, 12.1x45, 12.2, 12.3, 13.1, or 13.2
  2. Identify unnumbered interfaces
    Run 'show configuration interfaces' and look for 'unnumbered-interface' statements in the configuration
    Affected if Any interface is configured as unnumbered (uses 'unnumbered-interface lo0' or similar)
  3. Verify Proxy ARP status on unnumbered interfaces
    Run 'show configuration protocols arp' and check interface-specific proxy-arp settings, or run 'show arp' to inspect current ARP behavior; examine interface config for 'proxy-arp' under the unnumbered interface hierarchy
    Affected if Proxy ARP is enabled on an unnumbered interface (proxy-arp configuration present under the interface)

The system is affected if running an affected Junos version AND has Proxy ARP enabled on an unnumbered interface, as this specific combination allows the ARP poisoning attack vector.

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

Upgrade Junos to the fixed versions (10.4S15, 11.4R9, 11.4X27.44, 12.1R7, 12.1X44-D20, 12.1X45-D15, 12.2R6, 12.3R3, 13.1R3, 13.2R1 or later). Alternatively, if Proxy ARP is not required, disable it on unnumbered interfaces.

Recommended fix High confidence

Upgrade to the first fixed release in your current branch: 10.4S15, 11.4R9, 11.4X27.44, 12.1R7, 12.1X44-D20, 12.1X45-D15, 12.2R6, 12.3R3, 13.1R3, or 13.2R1 (whichever corresponds to your current branch)

  1. 1. Identify the current Junos version running on the device using 'show version'
  2. 2. Determine which branch (10.4S, 11.4R, 11.4X27, 12.1R, 12.1X44, 12.1X45, 12.2, 12.3, 13.1, or 13.2) is in use
  3. 3. Download the appropriate fixed release for the identified branch from the Juniper support portal (kb.juniper.net)
  4. 4. Upload the Junos upgrade package to the device using 'request system software add <package>' or via SCP/FTP
  5. 5. Reboot the device using 'request system reboot' to apply the upgrade
  6. 6. After reboot, verify the new version is running with 'show version' and confirm the fix is applied
  7. 7. Alternatively, if Proxy ARP on unnumbered interfaces is not required, disable it using 'set protocols arp interface <if-name> no-proxy-arp' under the respective interface configuration
Caveat Upgrading Junos may introduce compatibility issues with existing configurations or features; review Junos release notes for your specific upgrade path for any known issues

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-2013-6014 — 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-2013-6014 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