dbcve.org
Secure Firewall Threat DefenseApplication · Cisco

CVE-2017-3806

MEDIUM · 5.3 CVSS v3.0 Published 2017-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
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 CLI command processing in the Cisco Firepower 4100 Series Next-Generation Firewall and Cisco Firepower 9300 Security Appliance could allow an authenticated, local attacker to inject arbitrary shell commands that are executed by the device. More Information: CSCvb61343. Known Affected Releases: 2.0(1.68). Known Fixed Releases: 2.0(1.118) 2.1(1.47) 92.1(1.1646) 92.1(1.1763) 92.2(1.101).

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 command injection vulnerability exists in the CLI of Cisco Firepower 4100 Series Next-Generation Firewall and Firepower 9300 Security Appliance. An authenticated local attacker with CLI access can inject arbitrary shell commands that get executed with elevated privileges on the device due to insufficient input validation in CLI command processing.

MitigationApply the appropriate fixed software release (2.0(1.118), 2.1(1.47), 92.1(1.1646), 92.1(1.1763), 92.2(1.101) or later). As a compensating control, restrict CLI access to only trusted, authorized personnel and implement least-privilege access controls.

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
Secure Firewall Threat DefenseApplication
Affected:= 5.3.0= 5.4.0= 6.0.0= 6.0.1= 6.1.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 the Firepower product model
    Access the device CLI or management interface and run 'show version' or check the system dashboard to identify the exact model (Firepower 4100 Series NGFW, Firepower 9300 Security Appliance, or Firepower Threat Defense)
    Affected if The model is Cisco Firepower 4100 Series, Firepower 9300, or Firepower Threat Defense
  2. Check the Firepower Threat Defense version
    Run 'show version' in the CLI or check the management center for the installed FTD version number
    Affected if The installed version is exactly 5.3.0, 5.4.0, 6.0.0, 6.0.1, or 6.1.0
  3. Verify CLI access is enabled
    Confirm the CLI service is accessible by attempting to access the device console or SSH management interface
    Affected if CLI access is available (this is enabled by default on affected platforms)
  4. Check for low-privilege CLI accounts
    Review user accounts configured on the device using 'show user' or check the local user database to see if any non-admin accounts exist with CLI access
    Affected if Any authenticated user account exists with CLI access, regardless of privilege level, since the flaw allows privilege escalation

You are affected if you are running Cisco Firepower Threat Defense version 5.3.0, 5.4.0, 6.0.0, 6.0.1, or 6.1.0 (or Firepower 4100/9300 with corresponding vulnerable CLI code) and have any authenticated CLI access enabled.

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

Apply the appropriate fixed software release (2.0(1.118), 2.1(1.47), 92.1(1.1646), 92.1(1.1763), 92.2(1.101) or later). As a compensating control, restrict CLI access to only trusted, authorized personnel and implement least-privilege access controls.

Fix this in Secure Firewall Threat Defense Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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