dbcve.org
Firepower Management CenterApplication · Cisco

CVE-2024-20386

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability exists in Cisco Firepower Management Center web-based management interface due to insufficient input validation. An unauthenticated remote attacker can inject malicious script payloads into data fields that persist and execute when users interact with the affected interface.

MitigationApply the Cisco patch/更新 for CVE-2024-20386 when available; until then, limit FMC interface exposure to trusted networks and monitor for suspicious user activity.

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
Affected:= 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
Affected:= 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.11

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FMC product and version
    Log into the Firepower Management Center web interface and navigate to System > About > Updates, or run 'show version' via CLI to determine the exact version number
    Affected if The installed version matches any version listed in the affected versions for either Cisco Firepower Management Center or Cisco Secure Firewall Management Center
  2. Confirm web interface accessibility
    Determine if the FMC web-based management interface is reachable from network locations outside the trusted internal network
    Affected if The FMC web interface is exposed to untrusted or external networks (internet-accessible or reachable from less-trusted segments)
  3. Review recent system logs for XSS indicators
    Check FMC logs in System > Monitoring > Logs for entries containing script tags (<script>), javascript:, or other HTML injection patterns in user-definable fields such as device names, policies, or custom objects
    Affected if Logs contain unexpected HTML, JavaScript, or script tag content in fields where only plain text should exist
  4. Audit user-created objects and policies
    Review any user-created policy objects, custom application detectors, or network objects via the web interface for unexpected JavaScript code or suspicious URL patterns
    Affected if Any stored objects contain malicious script payloads that could execute when viewed by other users

A user is affected if the installed FMC version matches any of the listed affected versions AND the web interface is accessible (which is required for the XSS to be triggered).

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 the Cisco patch/更新 for CVE-2024-20386 when available; until then, limit FMC interface exposure to trusted networks and monitor for suspicious user activity.

Recommended fix Moderate confidence

Contact Cisco TAC for the specific fixed release for your FMC version branch (6.2.3.x, 6.4.0.x, 6.6.x, or 7.0.x)

  1. 1. Contact Cisco TAC or check the Cisco Firepower Management Center security advisory at sec.cloudapps.cisco.com for the specific fixed software release
  2. 2. Prior to upgrade, back up the FMC configuration
  3. 3. Schedule a maintenance window following Cisco's upgrade procedure for FMC
  4. 4. Upgrade the Firepower Management Center to the fixed release as specified in the Cisco security advisory
  5. 5. After upgrade, verify the web interface is functional and the XSS vulnerability is remediated
Caveat Ensure compatibility with managed devices before upgrading; review Cisco's upgrade guide for any prerequisites or migration steps

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

Fix this in Firepower Management Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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