Secure Firewall Management CenterApplication · Cisco
CVE-2023-20114
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 file download feature of Cisco Firepower Management Center (FMC) Software could allow an authenticated, remote attacker to download arbitrary files from an affected system. This vulnerability is due to a lack of input sanitation. An attacker could exploit this vulnerability by sending a crafted HTTPS request. A successful exploit could allow the attacker to download arbitrary files from the affected system.
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 confidencePath traversal vulnerability in Cisco FMC file download feature due to insufficient input sanitization, allowing authenticated remote attackers to download arbitrary system files via crafted HTTPS requests.
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.2.3, <= 6.2.3.18>= 6.4.0, <= 6.4.0.16>= 6.6.0, <= 6.6.7.1>= 7.0.0, <= 7.0.5>= 7.1.0, <= 7.1.0.3>= 7.2.0, <= 7.2.3.1>= 7.3.0, <= 7.3.1.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Verify Cisco FMC versionLog into the FMC web interface and navigate to Help > About, or run 'show version' via CLI to confirm the installed software versionAffected if Version falls within any of these ranges: 6.2.3-6.2.3.18, 6.4.0-6.4.0.16, 6.6.0-6.6.7.1, 7.0.0-7.0.5, 7.1.0-7.1.0.3, 7.2.0-7.2.3.1, or 7.3.0-7.3.1.1
-
Confirm FMC web interface accessibilityDetermine if the FMC HTTPS management interface (port 443) is reachable from networks outside your trusted administrative rangeAffected if The web interface is exposed to untrusted or external IP addresses without IP-based access restrictions
-
Review access logs for path traversal patternsInspect FMC logs or syslog exports for abnormal file download requests containing sequences such as '../', '..%2f', or absolute paths like '/etc/passwd' or 'c:\windows'Affected if Logs show file download requests with path traversal sequences targeting system files outside the expected download directory
-
Check for unauthorized file downloadsReview FMC audit logs for any file download events initiated by accounts or IP addresses that were not expected to perform such actionsAffected if Audit logs reveal file downloads initiated from unfamiliar source IPs or by users who do not typically access the file download feature
You are affected if the FMC version is within any of the listed affected ranges AND the web interface is accessible to untrusted users, or if logs show evidence of path traversal file download attempts.
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 Cisco's available patch; until then, restrict FMC administrative access to trusted IPs and monitor for suspicious file download patterns.
Upgrade to the first fixed release in your current major version line: 6.2.3.19+, 6.4.0.17+, 6.6.0.8+, or 7.0.6+ (or migrate to newer branches such as 7.1.x/7.2.x if available)
- 1. Identify the current version of Cisco Secure Firewall Management Center (FMC) by navigating to the FMC web interface and checking System > About > Updates, or via CLI using 'show version'.
- 2. Determine the appropriate fixed release for your current major version line: For 6.2.3.x upgrade to 6.2.3.19 or later; for 6.4.0.x upgrade to 6.4.0.17 or later; for 6.6.0.x upgrade to 6.6.0.8 or later; for 7.0.x upgrade to 7.0.6 or later.
- 3. Download the appropriate upgrade package from the Cisco Software Download Center (software.cisco.com).
- 4. Plan maintenance window as upgrades require system downtime.
- 5. Backup the FMC configuration before proceeding with the upgrade.
- 6. Upload the upgrade package to the FMC via the web interface (System > Updates > Product Updates) or via CLI.
- 7. Initiate the upgrade and monitor the process for completion.
- 8. Verify the upgrade was successful by checking the new version and ensuring all services are operational.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Secure Firewall Management Center
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20114 — 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-2023-20114 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