Secure Firewall Management CenterApplication · Cisco
CVE-2020-3311
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 interface of Cisco Firepower Management Center (FMC) Software could allow an unauthenticated, remote attacker to redirect a user to a malicious web page. The vulnerability is due to improper input validation of HTTP request parameters. An attacker could exploit this vulnerability by intercepting and modifying an HTTP request from a user. A successful exploit could allow the attacker to redirect the user to a specific malicious web page.
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 confidenceAn open redirect vulnerability in Cisco Firepower Management Center web interface allows unauthenticated remote attackers to modify HTTP request parameters and redirect users to malicious websites. The flaw stems from improper input validation of HTTP redirect parameters, enabling phishing and credential theft via the trusted FMC domain.
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
< 6.3.0CVSS 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.
-
Confirm Cisco FMC is deployedIdentify if the Cisco Firepower Management Center (also called Secure Firewall Management Center) web interface is accessible on your network. This is typically accessible via HTTPS on port 443 or 8443.Affected if The product is present in your environment
-
Identify the FMC versionLog into the FMC web interface and navigate to Help > About, or run 'show version' via CLI if you have SSH access to the FMC appliance.Affected if The installed version is below 6.3.0 (for example, 6.2.0, 6.1.0, 6.0.x, etc.)
-
Check web interface exposureDetermine if the FMC web management interface is externally accessible or exposed to untrusted networks. Review firewall rules and access lists governing access to the FMC HTTPS ports.Affected if The web interface is reachable from networks where untrusted or unauthenticated users could submit HTTP requests
-
Review HTTP access logs for redirect parametersExamine FMC web server logs (typically stored in /var/log/ or accessible via the web interface) for requests containing patterns like 'redirect=', 'url=', or 'next=' parameters pointing to external domains.Affected if Logs show unauthenticated requests with redirect parameters pointing to non-Cisco domains or suspicious URLs
You are affected if Cisco FMC version is below 6.3.0 and the web interface can be accessed by unauthenticated users who could inject malicious redirect parameters.
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 data6.3.0
Implement strict allowlist-based validation for redirect parameters and reject any values not matching approved destinations. Consider using indirect object references (mapping tokens to URLs server-side) rather than accepting raw URLs in parameters.
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
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 locallyCheck whether your project pulls in CVE-2020-3311 — 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-2020-3311 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