dbcve.org
Secure Firewall Management CenterApplication · Cisco

CVE-2018-0383

HIGH · 8.6 CVSS v3.0 Published 2018-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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 detection engine of Cisco FireSIGHT System Software could allow an unauthenticated, remote attacker to bypass a file policy that is configured to block the transfer of files to an affected system via FTP. The vulnerability exists because the affected software incorrectly handles FTP control connections. An attacker could exploit this vulnerability by sending a maliciously crafted FTP connection to transfer a file to an affected device. A successful exploit could allow the attacker to bypass a file policy that is configured to apply the Block upload with reset action to FTP traffic. Cisco Bug IDs: CSCvh70130.

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 vulnerability in the Cisco FireSIGHT System Software detection engine allows unauthenticated remote attackers to bypass file policies that block FTP file uploads. The software incorrectly handles FTP control connections, permitting specially crafted FTP transfers to evade block policies configured with 'Block upload with reset' action.

MitigationApply the Cisco patch for CSCvh70130 to obtain a fixed version of FireSIGHT System Software. As a temporary workaround, implement additional network-level controls or alternative file transfer restrictions until the patch can be deployed.

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.1= 6.2.3= 6.3.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
Changed
Confidentiality
None
Integrity
High
Availability
None

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

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

  1. Check the Cisco Secure Firewall Management Center version
    Log into the management center web interface and navigate to System > Updates, or run 'show version' via CLI to obtain the installed software version
    Affected if The installed version equals 6.2.2.1, 6.2.3, or 6.3.0 exactly
  2. Verify if file policies with 'Block upload with reset' action are configured
    In the web UI, navigate to Policies > File Policy and inspect each file policy. Look for rules where the Action column shows 'Block with Reset' for FTP file uploads
    Affected if Any file policy contains a rule with 'Block upload with reset' action applied to FTP traffic
  3. Confirm if the file policy is applied to access control or intrusion policies handling FTP
    Check the policy assignments under Policies > Access Control or the associated intrusion policy. Verify that the file policy from step 2 is linked to a policy handling FTP control connections
    Affected if A file policy with 'Block upload with reset' is active and processing FTP traffic flows
  4. Inspect FTP traffic handling logs for bypass indicators
    Use the management center dashboard or run AMP for Networks events query filtering for FTP file transfers. Look for file transfer events that were not blocked despite the policy configuration
    Affected if FTP upload events appear in the logs but were not blocked when a 'Block upload with reset' policy was expected to apply

You are affected if the installed version is exactly 6.2.2.1, 6.2.3, or 6.3.0 AND you have active file policies with 'Block upload with reset' action handling FTP traffic.

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 patch for CSCvh70130 to obtain a fixed version of FireSIGHT System Software. As a temporary workaround, implement additional network-level controls or alternative file transfer restrictions until the patch can be deployed.

Fix this in Secure Firewall Management Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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