dbcve.org
Secure Firewall Management CenterApplication · Cisco

CVE-2024-20377

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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) could allow an authenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the interface. This vulnerability is due to the web-based management interface not properly validating user-supplied input. An attacker could exploit this vulnerability by by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected 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 confidence

Stored cross-site scripting (XSS) vulnerability in Cisco Firepower Management Center web-based management interface due to improper input validation. Authenticated attackers can inject malicious scripts that execute in users' browsers when viewing crafted content.

MitigationApply Cisco's patch for FMC when available; until then, implement Content Security Policy headers and train users to avoid clicking untrusted links.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 version via CLI
    Log into the Firepower Management Center console and run the command `show version` or `system/version` to display the installed software version.
    Affected if The displayed version matches any of: 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, or 7.0.6.2
  2. Confirm web management interface is enabled
    Access the FMC web UI by navigating to the management IP in a browser. If the login page loads, the web interface is active.
    Affected if The web-based management interface is accessible and functional on your FMC device.
  3. Review user-created objects for suspicious content
    In the FMC web UI, navigate to Objects > Object Management and inspect any custom objects, network objects, or policy objects for unexpected script tags (<script>) or javascript: URIs.
    Affected if Any user-created objects contain encoded or plain script injection payloads that could execute in a browser.
  4. Examine audit and event logs for XSS attempts
    In the FMC web UI, go to Monitoring > Audit or System > Logs and search for entries containing typical XSS patterns such as <script, onerror=, onload=, or javascript:.
    Affected if Recent audit logs show authenticated users creating or modifying content with XSS payload patterns.

You are affected if your Cisco Secure Firewall Management Center runs any of the listed 7.0.x versions and has the web management interface enabled.

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 for FMC when available; until then, implement Content Security Policy headers and train users to avoid clicking untrusted links.

Recommended fix Moderate confidence

Cisco FMC 7.0.1.2 or later (refer to official Cisco advisory for exact fixed release)

  1. 1. Access the Cisco Firepower Management Center web-based management interface
  2. 2. Navigate to System > Updates > Product Updates to check for available updates
  3. 3. Alternatively, access the Cisco Security Advisory at sec.cloudapps.cisco.com for CVE-2024-20377 to identify the specific fixed release
  4. 4. Download and install the fixed version (or the latest available patch that addresses this vulnerability)
Caveat Review Cisco release notes for any compatibility or configuration changes between 7.0.x versions 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
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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