dbcve.org
Secure Firewall Management CenterApplication · Cisco

CVE-2024-20340

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 web-based management interface of Cisco Secure Firewall Management Center (FMC) Software, formerly Firepower Management Center Software, could allow an authenticated, remote attacker to perform an SQL injection attack against an affected device. To exploit this vulnerability, an attacker must have a valid account on the device with the role of Security Approver, Intrusion Admin, Access Admin, or Network Admin. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted HTTP request to the web-based management interface of an affected device. A successful exploit could allow the attacker to read the contents of databases on the affected device and also obtain limited read access to the underlying operating system.

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

SQL injection vulnerability in Cisco Secure Firewall Management Center web-based management interface allows authenticated attackers with Security Approver, Intrustion Admin, Access Admin, or Network Admin roles to send crafted HTTP requests, potentially reading database contents and gaining limited OS read access.

MitigationApply Cisco's patch when available; restrict administrative accounts to minimum necessary personnel; implement web application firewall rules to detect SQL injection patterns in HTTP requests.

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:= 7.0.0= 7.0.0.1= 7.0.1= 7.0.1.1= 7.0.2= 7.0.2.1= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.0.6.1= 7.0.6.2

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

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

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. Confirm Cisco Secure Firewall Management Center is installed
    Identify the product by running `show version` on the device CLI or checking the web interface login page for 'Cisco Secure Firewall Management Center' branding
    Affected if The device is running Cisco Secure Firewall Management Center (FMC)
  2. Check the FMC software version
    Run `show version` on the device CLI or view the version in the web interface under Help > About. Compare the version number to the affected list: 7.0.0, 7.0.0.1, 7.0.1, 7.0.1.1, 7.0.2, 7.0.2.1, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.6.1, 7.0.6.2
    Affected if The installed version matches any of the listed affected versions
  3. Verify the web-based management interface is enabled
    Check if the FMC web interface is accessible and enabled via `show http-server` CLI command or by attempting to reach the management interface over HTTPS
    Affected if The web-based management interface is enabled and reachable
  4. Identify accounts with vulnerable roles
    Review user accounts in the FMC web interface under System > Users > User Management or via `show user-account` CLI command. Look for accounts assigned Security Approver, Intrusion Admin, Access Admin, or Network Admin roles
    Affected if Any user accounts exist with Security Approver, Intrusion Admin, Access Admin, or Network Admin roles

The environment is affected if Cisco Secure Firewall Management Center is running any of versions 7.0.0 through 7.0.6.2, the web interface is enabled, and at least one account with the specified administrative roles exists.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco's patch when available; restrict administrative accounts to minimum necessary personnel; implement web application firewall rules to detect SQL injection patterns in HTTP requests.

Recommended fix Moderate confidence

Cisco Secure Firewall Management Center 7.0.2 or later

  1. 1. Identify the current installed version of Cisco Secure Firewall Management Center (FMC) by accessing the web-based management interface and navigating to System > About > Cisco Firepower Management Center.
  2. 2. Verify that the current version is one of the affected versions: 7.0.0, 7.0.0.1, 7.0.1, or 7.0.1.1.
  3. 3. Schedule a maintenance window for the upgrade, ensuring sufficient downtime is allocated.
  4. 4. Back up the FMC configuration and any necessary data before proceeding with the upgrade.
  5. 5. Download the fixed FMC software version (7.0.2 or later) from the Cisco Software Download center at software.cisco.com.
  6. 6. Upload the upgrade package to the FMC via the web interface (System > Updates > Product Updates).
  7. 7. Install the upgrade following the standard Cisco FMC upgrade procedure.
  8. 8. After upgrade completion, verify the new version is installed and the web interface is accessible.
Caveat Review Cisco release notes for 7.0.2+ for any configuration or compatibility changes before upgrading

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

Fix this in Secure Firewall Management Center Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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