Firepower Management CenterApplication · Cisco
CVE-2024-20372
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 · uneditedA vulnerability in the web-based management interface of Cisco Firepower Management Center (FMC) Software could allow an unauthenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the interface of an affected device. This vulnerability is due to insufficient validation of user-supplied input by the web-based management interface. An attacker could exploit this vulnerability by inserting crafted input into various data fields in an affected interface. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface, or access sensitive, browser-based information.
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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in the web-based management interface of Cisco Firepower Management Center (FMC) Software. An unauthenticated, remote attacker can inject malicious script into various data fields, which is then stored and executed when viewed by legitimate users, allowing arbitrary code execution in the browser context or access to sensitive browser-based information.
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
Firepower Management CenterApplication
= 6.4.0.17= 6.4.0.18= 6.6.7.2= 7.0.6.1= 7.0.6.2= 7.2.5.1= 7.2.5.2= 7.2.6= 7.2.7= 7.2.8= 7.2.8.1= 7.4.0
Secure Firewall Management CenterApplication
= 6.2.3= 6.2.3.1= 6.2.3.2= 6.2.3.3= 6.2.3.4= 6.2.3.5= 6.2.3.6= 6.2.3.7= 6.2.3.8= 6.2.3.9= 6.2.3.10= 6.2.3.11CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed FMC software versionLog into the FMC web interface and navigate to System > About > Updates, or run 'show version' via CLI to retrieve the installed software versionAffected if Version matches any of these: 6.4.0.17, 6.4.0.18, 6.6.7.2, 7.0.6.1, 7.0.6.2, 7.2.5.1, 7.2.5.2, 7.2.6, 7.2.7, 7.2.8, 7.2.8.1, 7.4.0 for Firepower Management Center; or 6.2.3 through 6.2.3.11 for Secure Firewall Management Center
-
Determine web interface exposureReview network access controls and firewall rules to determine if the FMC web management interface (HTTPS ports 443/8443) is accessible from untrusted networksAffected if The FMC web interface is exposed to the internet or untrusted internal networks without proper access restrictions
-
Inspect stored data fields for injected scriptsReview database entries or exported configuration data for any unexpected script tags, javascript: URIs, or HTML event handlers in fields such as device names, policy descriptions, object names, or user-defined text fieldsAffected if Any stored data fields contain suspicious patterns like <script>, javascript:, onload=, onerror=, or other XSS payloads that were not intentionally inserted by administrators
-
Examine browser execution contextAccess the FMC web interface using a browser with developer tools, navigate to various management pages, and inspect the DOM for any unexpected script execution or injected content in the user interfaceAffected if Scripts execute automatically or injected content appears in the UI when viewing normally managed pages without manually triggering any user actions
You are affected if your FMC version matches the listed affected versions AND the web interface is accessible to potential attackers, regardless of whether you can currently detect injected scripts.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor patch from Cisco's security advisory; in the interim, restrict access to the FMC web interface to trusted users only and monitor for suspicious input patterns in data fields.
Upgrade to FMC versions 6.4.0.19 or later (for 6.4.x), 6.7.0 or later (for 6.6.x), 7.1.0 or later (for 7.0.x), or 6.2.3.4 or later (for 6.2.3.x)
- 1. Access the Firepower Management Center web-based management interface
- 2. Navigate to System > Updates > Product Updates to check for available updates
- 3. Download and install the latest Cisco FMC software version that includes the fix for CVE-2024-20372
- 4. Alternatively, download the security update from the Cisco Software Download Center (software.cisco.com)
- 5. Before upgrading, backup the FMC configuration via System > Configuration > Database Backup
- 6. Schedule a maintenance window as the upgrade may require brief downtime
- 7. Install the upgrade following Cisco's standard FMC upgrade procedure
- 8. After upgrade, verify the system is functioning normally and the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firepower Management Center
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20372 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-20372 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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