ThreatPort
Login Register
CVE-2020-3187 CRITICAL

CVE-2020-3187 exposure check for Firepower Threat Defense

Check whether public-facing assets expose Cisco Firepower Threat Defense signals related to CVE-2020-3187. Severity: CRITICAL.

Start free scan View $50 Pricing

From CVE Record to External Exposure

A vulnerability in the web services interface of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to conduct directory traversal attacks and obtain read and delete access to sensitive files on a targeted system. The vulnerability is due to a lack of proper input validation of the HTTP URL. An attacker could exploit this vulnerability by sending a crafted HTTP request containing directory traversal character sequences. An exploit could allow the attacker to view or delete arbitrary files on the targeted system. When the device is reloaded after exploitation of this vulnerability, any files that were deleted are restored. The attacker can only view and delete files within the web services file system. This file system is enabled when the affected device is configured with either WebVPN or A...

Firepower Threat Defense vulnerability should be triaged by matching the affected vendor and product to live, internet-facing assets rather than treating the CVE as an abstract feed item. ThreatPort focuses on the first question that budget-constrained IT leaders and CISOs ask: what can an outside observer find today, how severe is it, and what should be fixed first?

Known Exploitation Record

Known ransomware campaign use
Not recorded
EPSS exploitation probability
96.59% (100p)
CVSS base score
9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)
Disclosed
2020-05-06
Weakness type
CWE-22

Source: CISA Known Exploited Vulnerabilities catalog and FIRST.org EPSS.

What ThreatPort Checks

Identify externally reachable services that appear related to Cisco Firepower Threat Defense.
Map detected technologies to CVE-2020-3187, severity context, and practical remediation priority.
Check TLS, DNS, headers, exposed panels, stale endpoints, and service fingerprints from a public attacker perspective.
Produce a concise scorecard first, then unlock deeper AI pentest evidence and PDF reporting when remediation planning begins.

The output is intentionally practical: ownership clues, risk context, remediation hints, and repeatable evidence that can be shared with technical teams or leadership. It is not positioned as magic compliance automation or a replacement for human security judgment.

Lean security teams rarely need another broad vulnerability list. They need to know whether an exposed endpoint, an expired certificate, a weak DNS setting, or a CVE-linked service is likely to affect the systems they actually run. ThreatPort scans from the outside in, ranks what it finds by real reachability rather than raw CVSS, and hands back evidence a team can act on the same day.

Route-Specific Evidence Profile

CVE-2020-3187 affects Cisco Firepower Threat Defense, a CWE-22 weakness. Disclosed 2020-05-06. This page exists to answer one question: is anything you own externally reachable and running it.

Assets This Page Should Care About

Public domains Subdomains Externally reachable web apps TLS endpoints DNS records

Signals Worth Prioritizing

Forgotten subdomains
Weak DNS or email controls
Outdated services
Risky headers

What Should Be Reviewed First in This Context?

For teams running Cisco Firepower Threat Defense, the first step is to validate internet-facing assets with business relevance instead of producing a generic vulnerability list.

Forgotten subdomains
Weak DNS or email controls
Outdated services
Risky headers

Action Checklist

  1. Confirm whether Firepower Threat Defense is present on any public domain, subdomain, API, or admin surface.
  2. Prioritize CRITICAL exposure only when the affected service is reachable or business-critical.
  3. Patch, disable, isolate, or put compensating controls in front of the affected service.
  4. Re-scan after remediation to capture before-and-after evidence for technical teams or leadership.

Context-Aware Next Fixes

  1. Verify ownership of exposed assets
  2. Close unnecessary public services
  3. Remediate the highest-confidence exposed findings first, then re-scan to prove closure.

Useful evidence for this context usually maps to ISO 27001, SOC 2, vendor security reviews. ThreatPort keeps the language cautious: this is operational security evidence, not a legal certification or a guarantee that every auditor will accept a generated report without review.