Firepower Management CenterApplication · Cisco
CVE-2024-20410
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 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 confidenceA stored XSS vulnerability exists in Cisco FMC's web-based management interface due to insufficient input validation. An unauthenticated remote attacker can inject malicious JavaScript into data fields (e.g., device names, policies, objects) that persist and execute when legitimate users view the affected interface, enabling session hijacking or information theft.
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.
-
Identify FMC versionLog in to the Firepower Management Center web interface, navigate to System > About > Cisco Firepower Management Center (or System > Configuration > Updates > About), and record the exact version number displayed.Affected if The displayed version matches any version listed in the affected products: 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; or 6.2.3 through 6.2.3.11 for Secure Firewall.
-
Check management interface exposureReview network firewall rules and access policies to determine whether the FMC web-based management interface (HTTPS on port 443 or custom SSL port) is accessible from networks outside your trusted internal networks, including the internet.Affected if The FMC web interface is reachable from untrusted or external networks without VPN or jump host requirements.
-
Search for injected scripts in device namesIn the FMC web interface, navigate to Devices > Device Management, and manually inspect each device name and hostname for any unexpected characters, HTML tags, or script content that does not match your expected naming convention.Affected if Any device name contains visible script tags, JavaScript event handlers, or unexpected encoded characters that were not intentionally configured.
-
Review policy and object names for suspicious contentNavigate to Policies, Objects, and other configuration areas within the FMC interface, and inspect policy names, object names, and descriptions for any foreign script content or malformed input.Affected if Any policy, object, or description field contains script tags, URL-encoded characters that decode to script content, or content you did not intentionally create.
You are affected if your FMC version matches any listed affected version AND the management interface is accessible to untrusted users, regardless of whether malicious content is currently visible in the interface.
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.
From vendor dataApply Cisco's available patch for FMC; until then, restrict management interface access to trusted networks only and monitor for suspicious content in interface fields.
Fix this in Firepower Management Center
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20410 — 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-20410 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