Secure Firewall Management CenterApplication · Cisco

CVE-2019-1699

HIGH · 7.8 CVSS v3.0 Published 2019-05-03
Fix available
A fix is available. Upgrade to 6.2.3.12 or later.
See remediation →
80/100
Remediation priority · High
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 CLI of Cisco Firepower Threat Defense (FTD) Software could allow an authenticated, local attacker to perform a command injection attack. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by injecting commands into arguments for a specific command. A successful exploit could allow the attacker to execute commands 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 command injection vulnerability exists in the Cisco Firepower Threat Defense (FTD) CLI where insufficient input validation allows an authenticated local attacker to inject OS commands through arguments of a specific CLI command, achieving root-level execution privileges.

MitigationApply the Cisco security patch for CVE-2019-1699. Prior to patching, restrict local CLI access to trusted administrators only and monitor for unusual command patterns.

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 Management CenterApplication
Affected:< 6.2.3.12

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

CVSS:3.0/AV:L/AC:L/PR:L/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. Identify the Cisco product and version
    Access the Cisco Firepower Management Center or Firepower Threat Defense management interface and locate the system version information, typically found in the Device > Device Management or System > Licenses section
    Affected if The installed version is Cisco Secure Firewall Management Center (or Firepower Management Center) and the version number is below 6.2.3.12
  2. Verify CLI access is enabled
    Check if the command-line interface access is available for local authentication on the affected device. This is typically accessible via console, SSH, or direct terminal access to the FTD appliance
    Affected if CLI access is enabled and accessible to authenticated local users
  3. Identify local administrative accounts
    Review the list of locally configured administrator accounts that have CLI privileges. Check User Management or admin account settings within the FTD management interface
    Affected if There are local administrator accounts configured with CLI access privileges
  4. Review command logs for suspicious activity
    Examine CLI command history, audit logs, or system logs for any unusual or unexpected commands that may indicate exploitation, particularly commands containing shell metacharacters or unexpected OS-level operations
    Affected if Logs show commands originating from CLI that were not issued by authorized administrators or contain injected syntax

Environment is affected if running Cisco Secure Firewall Management Center below version 6.2.3.12 with CLI access enabled for any local authenticated user account

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.2.3.12 or later
Fixed in 6.2.3.12
Interim mitigation

Apply the Cisco security patch for CVE-2019-1699. Prior to patching, restrict local CLI access to trusted administrators only and monitor for unusual command patterns.

Fix this in Secure Firewall Management Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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