dbcve.org
JunosOperating system · Juniper

CVE-2014-3818

HIGH · 7.8 CVSS v2.0 Published 2014-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Junos OS 9.1 through 11.4 before 11.4R11, 12.1 before R10, 12.1X44 before D40, 12.1X46 before D30, 12.1X47 before D11 and 12.147-D15, 12.1X48 before D41 and D62, 12.2 before R8, 12.2X50 before D70, 12.3 before R6, 13.1 before R4-S2, 13.1X49 before D49, 13.1X50 before 30, 13.2 before R4, 13.2X50 before D20, 13.2X51 before D25, 13.2X52 before D15, 13.3 before R2, and 14.1 before R1, when supporting 4-byte AS numbers and a BGP peer does not, allows remote attackers to cause a denial of service (memory corruption and RDP routing process crash and restart) via crafted transitive attributes in a BGP UPDATE.

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 corruption vulnerability exists in Juniper Junos OS when the device supports 4-byte AS numbers but connects to a BGP peer that does not. Remote attackers can send crafted transitive attributes in BGP UPDATE messages, causing the routing process (rpd) to crash and restart, resulting in denial of service.

MitigationUpgrade Junos OS to the specified fixed versions (11.4R11, 12.1X44 D40, 12.1X46 D30, 12.1X47 D11, 12.2R8, 13.1R4-S2, 13.2R4, 13.3R2, or 14.1R1 or later). If immediate patching is not possible, consider restricting BGP peer connections or implementing BGP attribute filtering at network edges.

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:= 9.1= 9.2= 9.4= 9.5= 9.6= 10.0= 10.1= 10.2= 10.3= 10.4= 10.4r= 10.4s

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 the installed Junos OS version
    Run 'show version' or 'request system software version' to obtain the exact Junos version installed on the device
    Affected if The installed version matches any of these: 9.1, 9.2, 9.4, 9.5, 9.6, 10.0, 10.1, 10.2, 10.3, 10.4, 10.4r, or 10.4s
  2. Verify 4-byte AS number support is enabled
    Run 'show bgp neighbor' or check the BGP configuration with 'show configuration protocols bgp' to see if the local AS number is greater than 65535, or if 'asn-4byte' or similar 4-byte AS configuration is present
    Affected if The local AS number configured on the device exceeds 65535 (4-byte AS) or 4-byte AS support is explicitly enabled in the BGP configuration
  3. Identify BGP peers and their capabilities
    Run 'show bgp neighbor' and look for peers where the 'AS' field shows a 4-byte AS number but the neighbor's capability advertisement does not include 4-byte AS support, or check if any peer is configured with a 2-byte AS
    Affected if The device has BGP peers that do not advertise 4-byte AS number capability while the local device supports 4-byte AS numbers
  4. Confirm BGP is actively configured and running
    Run 'show bgp summary' to verify that BGP is enabled and there are active BGP peer sessions
    Affected if BGP is enabled and there are configured BGP peers

The device is affected if it runs a vulnerable Junos version (9.1 through 10.4s), has 4-byte AS number support enabled or configured with an AS number > 65535, and has at least one BGP peer that does not support 4-byte AS numbers.

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 OS to the specified fixed versions (11.4R11, 12.1X44 D40, 12.1X46 D30, 12.1X47 D11, 12.2R8, 13.1R4-S2, 13.2R4, 13.3R2, or 14.1R1 or later). If immediate patching is not possible, consider restricting BGP peer connections or implementing BGP attribute filtering at network edges.

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-3818 — 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-3818 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