dbcve.org
Secure Firewall Management CenterApplication · Cisco

CVE-2020-3307

MEDIUM · 5.3 CVSS v3.1 Published 2020-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 UI of Cisco Firepower Management Center (FMC) Software could allow an unauthenticated, remote attacker to write arbitrary entries to the log file on an affected device. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to send incorrect information to the system log on 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 · high confidence

A log injection vulnerability exists in the Cisco Firepower Management Center web UI where insufficient input validation allows unauthenticated remote attackers to send crafted HTTP requests that write arbitrary entries to the system log file. This could be used to obscure legitimate log entries or poison logs for forensic evasion.

MitigationApply the Cisco FMC software update addressing CVE-2020-3307. As an interim control, restrict network access to the FMC web interface to trusted management networks only.

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:= 6.2.2= 6.2.3= 6.3.0= 6.4.0= 6.5.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cisco FMC product type
    Identify the installed product as Cisco Firepower Management Center or Cisco Secure Firewall Management Center. This vulnerability only affects the management center, not individual firewall devices.
    Affected if The product is any version of Cisco Firepower Management Center or Cisco Secure Firewall Management Center.
  2. Check FMC software version
    Access the FMC web UI and navigate to System > Updates, or run 'show version' via CLI if you have console access. Record the exact version number (for example: 6.2.2, 6.2.3, 6.3.0, 6.4.0, or 6.5.0).
    Affected if The installed version is exactly 6.2.2, 6.2.3, 6.3.0, 6.4.0, or 6.5.0.
  3. Verify web UI is enabled and accessible
    Confirm the FMC web interface is enabled and network-accessible. Check via the FMC console under System > Configuration > Management Access, or attempt to reach the web UI URL from a management station.
    Affected if The FMC web UI is enabled and reachable over the network.
  4. Inspect system logs for anomalies
    Review FMC system logs (/var/log/messages or via the web UI logs viewer) for any unexpected or injected log entries that do not correspond to known administrative actions, particularly entries with unusual timestamps, source IPs, or malformed content.
    Affected if Log file contains entries that appear fabricated, obscured, or do not match legitimate recorded activities.

You are affected if you are running Cisco Secure Firewall Management Center versions 6.2.2, 6.2.3, 6.3.0, 6.4.0, or 6.5.0 with the web UI enabled and accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco FMC software update addressing CVE-2020-3307. As an interim control, restrict network access to the FMC web interface to trusted management networks only.

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
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

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