dbcve.org
Sd WanApplication · Cisco

CVE-2018-15387

CRITICAL · 9.8 CVSS v3.1 Published 2018-10-05
Fix available
A fix is available. Upgrade to 17.2.8 or later.
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
A vulnerability in the Cisco SD-WAN Solution could allow an unauthenticated, remote attacker to bypass certificate validation on an affected device. The vulnerability is due to improper certificate validation. An attacker could exploit this vulnerability by supplying a system image signed with a crafted certificate to an affected device, bypassing the certificate validation. An exploit could allow an attacker to deploy a crafted system image.

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 · moderate confidence

A vulnerability in Cisco SD-WAN Solution allows an unauthenticated remote attacker to bypass certificate validation due to improper handling of certificate checks. An attacker can exploit this by supplying a system image signed with a crafted certificate, bypassing the validation mechanism and allowing deployment of a malicious system image.

MitigationApply Cisco's patch for this vulnerability when available; ensure only images from trusted, validated sources are deployed to affected SD-WAN devices.

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
Sd WanApplication
Affected:>= 17.2.0, < 17.2.8= 18.3.0

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Check the installed SD-WAN software version
    Run 'show version' or 'show software' command on the SD-WAN device CLI to obtain the running software version
    Affected if The version is 17.2.0 through 17.2.7 (any version >= 17.2.0 but < 17.2.8), or exactly version 18.3.0
  2. Verify if image signature validation is enabled
    Check the SD-WAN configuration for image validation settings using 'show configuration' or review the image loading policies
    Affected if Signature validation is disabled or set to bypass for system images
  3. Review recently loaded system images
    Use 'show software history' or review image installation logs to list recently deployed system images
    Affected if Any system image was loaded from an untrusted or unauthorized source
  4. Inspect certificate configuration
    Run 'show certificate' or 'show crypto' commands to examine installed certificates and validation policies
    Affected if Non-default or unexpected certificates are present, or certificate chain validation appears weakened
  5. Check for image verification status
    Run 'show software integrity' or 'verify image' commands to confirm each deployed image's signature verification status
    Affected if Any currently running or备用 system image shows as unsigned, invalid, or bypassed

A system is affected if it runs any SD-WAN version 17.2.0 through 17.2.7 or exactly 18.3.0 AND has image signature validation disabled, bypassed, or has accepted an unsigned/untrusted system image.

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
Upgrade available Upgrade to 17.2.8 or later
Fixed in 17.2.8
Interim mitigation

Apply Cisco's patch for this vulnerability when available; ensure only images from trusted, validated sources are deployed to affected SD-WAN devices.

Recommended fix Moderate confidence

Cisco SD-WAN vManage version 17.2.8 or later (or any release above 18.3.0 if available)

  1. Identify the current Cisco SD-WAN vManage version by checking the system information or running 'show version' command
  2. Schedule a maintenance window for the upgrade procedure
  3. Download Cisco SD-WAN release 17.2.8 or later from the Cisco software download portal
  4. Upload the new system image to the SD-WAN vManage controller
  5. Follow Cisco standard upgrade procedures: initiate the upgrade through vManage web interface or CLI using 'request software install' command
  6. Verify the upgrade completed successfully and the system is running the fixed version
  7. Confirm the certificate validation is now functioning properly
Caveat Review Cisco release notes for any configuration or behavioral changes between your current version and 17.2.8; test in non-production environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sd Wan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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