Secure Firewall Management CenterApplication · Cisco
CVE-2019-12701
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 and malware inspection feature of Cisco Firepower Management Center (FMC) Software could allow an unauthenticated, remote attacker to bypass the file and malware inspection policies on an affected system. The vulnerability exists because the affected software insufficiently validates incoming traffic. An attacker could exploit this vulnerability by sending a crafted HTTP request through an affected device. A successful exploit could allow the attacker to bypass the file and malware inspection policies and send malicious traffic through the affected 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 · moderate confidenceThis vulnerability in Cisco Firepower Management Center allows an unauthenticated remote attacker to bypass file and malware inspection policies by sending specially crafted HTTP requests. The affected software insufficiently validates incoming traffic, allowing malicious files to pass through the device without being inspected.
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
all versions
Vdb Fingerprint DatabaseDatabase / datastore
< 327CVSS 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
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/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.
-
Identify Cisco Firepower Management Center deploymentConfirm the system in question is Cisco Firepower Management Center (FMC) or Cisco Secure Firewall Management Center. This is typically the centralized management console for Cisco firewall devices.Affected if The system is confirmed to be Cisco FMC or Secure Firewall Management Center.
-
Check Vdb Fingerprint Database versionAccess the FMC management interface and navigate to the Vdb/Fingerprints section, typically found under System > Updates or Extensions. Record the installed Vdb Fingerprint Database version number.Affected if The installed Vdb Fingerprint Database version is below 327.
-
Verify file and malware inspection policies existIn the FMC console, review the Access Control Policies or File Policies section. Check whether any policies are configured that perform file inspection, malware detection, or AMP (Advanced Malware Protection) on traffic.Affected if File inspection or malware detection policies are configured and applied to traffic flows.
-
Confirm HTTP traffic handlingReview the Access Control Policy rules that handle HTTP traffic. Identify if the policy allows or inspects HTTP traffic destined for downstream firewall devices managed by this FMC.Affected if The FMC is configured to handle or pass-through HTTP traffic that should be subject to inspection.
A user is affected if they run Cisco FMC with Vdb Fingerprint Database version below 327 AND have file/malware inspection policies configured for HTTP traffic, as the vulnerability allows malicious files to bypass those policies.
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 data327
Apply the Cisco software update for FMC when available, or implement additional layer 7 filtering/validation upstream to inspect HTTP traffic before it reaches the FMC.
Fix this in Secure Firewall Management Center
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12701 — 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-2019-12701 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