dbcve.org
JunosOperating system · Juniper

CVE-2015-5362

HIGH · 9.3 CVSS v2.0 Published 2015-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 BFD daemon in Juniper Junos OS 12.1X44 before 12.1X44-D50, 12.1X46 before 12.1X46-D35, 12.1X47 before 12.1X47-D25, 12.3 before 12.3R10, 12.3X48 before 12.3X48-D15, 13.2 before 13.2R8, 13.3 before 13.3R6, 14.1 before 14.1R5, 14.1X50 before 14.1X50-D85, 14.1X55 before 14.1X55-D20, 14.2 before 14.2R3, 15.1 before 15.1R1, and 15.1X49 before 15.1X49-D10 allows remote attackers to cause a denial of service (bfdd crash and restart) or execute arbitrary code via a crafted BFD packet.

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

The BFD (Bidirectional Forwarding Detection) daemon in Juniper Junos OS contains a memory corruption vulnerability when processing specially crafted BFD packets. A remote unauthenticated attacker can send a malicious BFD packet to trigger either a denial of service (bfdd process crash and restart) or potentially execute arbitrary code with elevated privileges.

MitigationApply the vendor-supplied Junos OS patches (12.1X44-D50 and later, 12.1X46-D35 and later, etc.) to the affected devices. Until patching is possible, consider filtering BFD traffic at network boundaries or disabling BFD on untrusted 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:= 12.1x44= 12.1x46= 12.1x47= 12.3= 12.3x48= 13.2= 13.3= 14.1= 14.1x53= 14.2= 15.1= 15.1x49

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/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 OS version
    Run 'show version' or 'show version detail' on the device CLI and compare the firmware version against the affected list: 12.1X44, 12.1X46, 12.1X47, 12.3, 12.3X48, 13.2, 13.3, 14.1, 14.1X53, 14.2, 15.1, 15.1X49
    Affected if The device runs any version matching exactly one of the listed affected versions
  2. Verify BFD protocol is configured
    Run 'show configuration | find bfd' or 'show protocols bfd' to see if BFD protocol is enabled in the device configuration
    Affected if BFD protocol configuration exists on the device (any BFD-enabled configuration)
  3. Identify BFD-enabled interfaces
    Run 'show bfd session' and review the configuration output to list all interfaces with active BFD sessions or BFD configuration
    Affected if Any interface has BFD sessions configured or active
  4. Assess BFD network exposure
    Review the identified BFD-enabled interfaces against your network topology to determine if they are reachable from untrusted or external networks
    Affected if BFD traffic from untrusted sources can reach the device (e.g., BFD enabled on WAN, transit, or internet-facing interfaces without filtering)

The device is affected if it runs an affected Junos version AND has BFD enabled on any interface that is reachable from untrusted network segments.

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

Apply the vendor-supplied Junos OS patches (12.1X44-D50 and later, 12.1X46-D35 and later, etc.) to the affected devices. Until patching is possible, consider filtering BFD traffic at network boundaries or disabling BFD on untrusted interfaces.

Recommended fix High confidence

Upgrade to the first fixed version in your current branch (e.g., 12.3R10 for 12.3 branch, 14.1R5 for 14.1 branch, 15.1X49-D10 for 15.1X49 branch)

  1. 1. Identify the current Junos OS version running on the device using 'show version'
  2. 2. Determine which branch (12.1X44, 12.1X46, 12.1X47, 12.3, 12.3X48, 13.2, 13.3, 14.1, 14.1X50, 14.1X55, 14.2, 15.1, or 15.1X49) the current version belongs to
  3. 3. Download the appropriate fixed version for that branch from the Juniper support portal: 12.1X44-D50+, 12.1X46-D35+, 12.1X47-D25+, 12.3R10+, 12.3X48-D15+, 13.2R8+, 13.3R6+, 14.1R5+, 14.1X50-D85+, 14.1X55-D20+, 14.2R3+, 15.1R1+, or 15.1X49-D10+
  4. 4. Upload the Junos upgrade package to the device via SCP or USB
  5. 5. Install the upgrade using 'request system software add <package-name>' command
  6. 6. Reboot the device using 'request system reboot' to apply the changes
  7. 7. After reboot, verify the BFD daemon is running using 'show bfd session' and confirm the new version with 'show version'
Caveat Review Juniper release notes for any compatibility changes; some legacy BFD configurations may need adjustment after upgrade

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
  • 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-2015-5362 — 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-2015-5362 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