dbcve.org
Secure Firewall Management CenterApplication · Cisco

CVE-2024-20374

HIGH · 7.2 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 →
78/100
Remediation priority · High
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 with Administrator-level privileges to execute arbitrary commands on the underlying operating system. This vulnerability is due to insufficient input validation of certain HTTP request parameters that are sent to the web-based management interface. An attacker could exploit this vulnerability by authenticating to the Cisco FMC web-based management interface and sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to execute commands as the root user on the affected device. To exploit this vulnerability, an attacker would need Administrator-level credentials.

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

Cisco Secure Firewall Management Center contains a command injection vulnerability in its web-based management interface due to insufficient validation of HTTP request parameters. An authenticated attacker with Administrator privileges can send crafted HTTP requests to execute arbitrary commands as root on the underlying operating system.

MitigationApply the vendor-supplied patch when available; restrict access to the FMC web management interface to trusted networks and enforce strong Administrator credentials to reduce exploitability.

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.7.0= 6.7.0.1= 6.7.0.2= 6.7.0.3= 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

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

CVSS:3.1/AV:N/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. Confirm product is Cisco Secure Firewall Management Center
    Identify the installed product by checking the system inventory or running 'show version' on the device. This vulnerability affects only the FMC, not other Cisco security products.
    Affected if The device is not a Cisco Secure Firewall Management Center instance.
  2. Check FMC version number
    Access the FMC web interface and navigate to Help > About, or run 'show version' via CLI to obtain the exact software version number.
    Affected if The installed version matches any of these: 6.7.0, 6.7.0.1, 6.7.0.2, 6.7.0.3, 7.0.0, 7.0.0.1, 7.0.1, 7.0.1.1, 7.0.2, 7.0.2.1, 7.0.3, or 7.0.4.
  3. Verify web-based management interface is enabled
    Check if the FMC web UI is accessible and running. This can be confirmed by attempting to reach the FMC HTTPS interface or reviewing the httpd service status via CLI with 'show running-config | include http'
    Affected if The FMC web-based management interface is exposed and accessible.
  4. Review Administrator accounts for unauthorized changes
    Log into the FMC web interface and navigate to System > Users > Administrators to review all Administrator-level accounts. Check for any unexpected or unauthorized administrator accounts that may indicate prior exploitation.
    Affected if New or unrecognized Administrator accounts exist that were not created by your organization.
  5. Inspect system logs for suspicious command execution
    Review FMC logs under System > Logs > Audit and search for unusual or unexpected CLI commands, particularly those executed via the web interface that involve shell execution or system-level operations.
    Affected if Audit logs show unexpected commands or API calls that were not initiated by legitimate administrators.

You are affected if the device is a Cisco Secure Firewall Management Center running any of the listed versions with its web management interface accessible to an authenticated administrator.

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 vendor-supplied patch when available; restrict access to the FMC web management interface to trusted networks and enforce strong Administrator credentials to reduce exploitability.

Fix this in Secure Firewall Management Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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