CVE-2021-34762
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 authenticated, remote attacker to perform a directory traversal attack on an affected device. The attacker would require valid device credentials. The vulnerability is due to insufficient input validation of the HTTPS URL by the web-based management interface. An attacker could exploit this vulnerability by sending a crafted HTTPS request that contains directory traversal character sequences to an affected device. A successful exploit could allow the attacker to read or write arbitrary files on the device.
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 directory traversal vulnerability in Cisco Firepower Management Center's web-based management interface allows authenticated attackers to read or write arbitrary files by sending crafted HTTPS requests with directory traversal character sequences (e.g., ../../). The vulnerability stems from insufficient input validation of the HTTPS URL by the interface.
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= 6.2.3= 6.4.0= 6.5.0= 6.6.1= 6.6.2= 6.6.3= 6.6.4= 6.7.0= 7.0.0= 7.1.0< 6.4.0.13>= 6.5.0, < 6.6.5>= 6.7.0, < 6.7.0.3>= 7.0.0, < 7.0.1= 6.2.3= 6.4.0= 6.5.0= 6.6.1= 6.6.2= 6.6.3= 6.6.4= 7.0.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 the installed Cisco productLog into the device CLI or check the system overview in the web interface to confirm the product name (Firepower Management Center Virtual Appliance, Sourcefire Defense Center, or Firepower Threat Defense)Affected if The product is not one of the three listed (FMC Virtual Appliance, Sourcefire Defense Center, or Firepower Threat Defense)
-
Determine the software versionRun the command 'show version' in the CLI, or check the Dashboard > System > Summary in the web interface to locate the installed version numberAffected if The version matches or falls within the affected ranges: FMC Virtual Appliance or Sourcefire Defense Center versions 6.2.3, 6.4.0, 6.5.0, 6.6.1-6.6.4, 7.0.0, 7.1.0; or FTD versions < 6.4.0.13, >= 6.5.0 and < 6.6.5, >= 7.0.0 and < 7.0.1, or >= 6.7.0 and < 6.7.0.3
-
Verify the web-based management interface is accessibleConfirm that the HTTPS management interface (typically port 443) is enabled and reachable on the device. Check via 'show interface' or review the management access configuration in the CLIAffected if The HTTPS web management interface is enabled and exposed (this is the attack surface for the vulnerability)
-
Confirm authentication methodReview whether local or remote administrator accounts are configured for the web interface by checking 'show admin-user' or reviewing the authentication settings in the web UI under System > Users > UsersAffected if The web management interface has any authenticated user accounts configured (authentication is required for exploitation)
The environment is affected if it runs an affected Firepower product (FMC Virtual Appliance, Sourcefire Defense Center, or Firepower Threat Defense) with a version matching the affected ranges AND has the HTTPS web management interface enabled and accessible to authenticated administrators.
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 · scoped6.4.0.136.6.56.7.0.3
Apply the vendor patch from Cisco when available, and limit access to the FMC web management interface to trusted administrators only until the patch is applied.
FMC: 6.7.0+ | FTD: 6.4.0.13, 6.6.5, 7.0.1, or 7.0.3+ depending on current branch
- 1. Identify the currently installed Cisco Firepower Management Center (FMC) or Firepower Threat Defense (FTD) version using 'show version' command
- 2. Determine which product line and version bracket your device falls into from the affected versions list
- 3. For Firepower Management Center Virtual Appliance or Sourcefire Defense Center: Upgrade to version 6.7.0 or later
- 4. For Firepower Threat Defense: If running < 6.4.0, upgrade to 6.4.0.13 or later; if running 6.5.0-6.6.4, upgrade to 6.6.5 or later; if running 6.7.0-6.7.0.2, upgrade to 7.0.3 or later; if running 7.0.0-7.0.0, upgrade to 7.0.1 or later
- 5. Download the appropriate firmware from Cisco's Software Download page (software.cisco.com) using valid Cisco credentials
- 6. Follow Cisco's standard upgrade procedure for FMC or FTD platforms, typically via the web UI or CLI
- 7. After upgrade, verify the new version is installed with 'show version' and confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34762 — 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-2021-34762 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