Secure Firewall Threat DefenseApplication · Cisco

CVE-2019-12694

MEDIUM · 6.7 CVSS v3.1 Published 2019-10-02
Fix available
A fix is available. Upgrade to 6.3.0.5 / 6.4.0.4 or later.
See remediation →
69/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 the command line interface (CLI) of Cisco Firepower Threat Defense (FTD) Software could allow an authenticated, local attacker with administrative privileges to execute commands on the underlying operating system with root privileges. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by executing a specific CLI command that includes crafted arguments. A successful exploit could allow the attacker to execute commands on the underlying OS with root privileges.

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 local privilege escalation vulnerability in Cisco Firepower Threat Defense (FTD) CLI allows authenticated administrators with existing privileges to execute arbitrary operating system commands with root privileges due to insufficient input validation when specific CLI commands with crafted arguments are executed.

MitigationApply the Cisco security patch/upgrade to a fixed version of FTD software as specified in the Cisco advisory; this is a software-only fix requiring a version upgrade.

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:< 6.3.0.5>= 6.4.0, < 6.4.0.4

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

CVSS:3.1/AV:L/AC:L/PR:H/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. Determine installed FTD version
    Access the FTD CLI and run the command 'show version' or 'show running-config | include version' to display the installed software version
    Affected if The displayed version falls within < 6.3.0.5 or >= 6.4.0 and < 6.4.0.4
  2. Compare version against affected ranges
    Review the version output from step 1 against the known affected ranges: versions prior to 6.3.0.5, and versions 6.4.0 through 6.4.0.3
    Affected if The installed version matches one of these ranges (< 6.3.0.5 or >= 6.4.0, < 6.4.0.4)
  3. Verify CLI access is enabled
    Confirm that the FTD CLI management interface is accessible and authentication is configured. Check via 'show managers' or review management access settings
    Affected if CLI management is enabled and user authentication is configured for administrative access
  4. Check for vulnerable CLI command behavior
    Test or audit CLI command execution with privileged admin accounts. The vulnerability allows privilege escalation when specific CLI commands accept crafted arguments
    Affected if An authenticated administrator with standard privileges can execute arbitrary OS commands with root privileges through the CLI

The environment is affected if the installed FTD version is less than 6.3.0.5 or falls between 6.4.0 and 6.4.0.3, and the CLI interface is accessible to authenticated administrators.

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
Upgrade available Upgrade to 6.3.0.5 / 6.4.0.4 or later
Fixed in 6.3.0.56.4.0.4
Interim mitigation

Apply the Cisco security patch/upgrade to a fixed version of FTD software as specified in the Cisco advisory; this is a software-only fix requiring a version upgrade.

Fix this in Secure Firewall Threat Defense Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2019-12694 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