dbcve.org
Secure Firewall Management CenterApplication · Cisco

CVE-2018-0333

MEDIUM · 5.8 CVSS v3.0 Published 2018-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/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 VPN configuration management of Cisco FireSIGHT System Software could allow an unauthenticated, remote attacker to bypass VPN security due to unintended side effects of dynamic configuration changes that could allow an attacker to bypass configured policies. The vulnerability is due to incorrect management of the configured interface names and VPN parameters when dynamic CLI configuration changes are performed. An attacker could exploit this vulnerability by sending packets through an interface on the targeted device. A successful exploit could allow the attacker to bypass configured VPN policies. Cisco Bug IDs: CSCvh49388.

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 confidence

A vulnerability in Cisco FireSIGHT System Software's VPN configuration management allows unauthenticated remote attackers to bypass VPN policies. The flaw stems from incorrect handling of interface names and VPN parameters when dynamic CLI configuration changes occur, causing unintended side effects that can be exploited by sending packets through an interface on the targeted device.

MitigationApply the vendor patch from Cisco for bug CSCvh49388 or upgrade to a fixed software version as specified in the Cisco security advisory.

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

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
Low
Integrity
None
Availability
None

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

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

  1. Identify the Cisco management platform
    Determine if the device is running Cisco Secure Firewall Management Center (formerly FireSIGHT System Software) by checking the system hostname, model information, or management interface access
    Affected if The system is confirmed to be a Cisco Secure Firewall Management Center (FireSIGHT) device
  2. Check the installed software version
    Access the system via admin CLI or web interface and retrieve the current software version number
    Affected if The installed version equals 6.2.2 exactly (the only version listed as affected in the advisory)
  3. Verify VPN policy configuration
    Review the VPN policies configured on the device through the management console, checking for any active VPN tunnels, site-to-site or remote-access VPN configurations
    Affected if VPN policies or tunnels are configured on the device
  4. Review interface and VPN parameter settings
    Inspect the interface configurations and VPN parameter bindings in the device configuration, specifically looking at how interfaces are assigned to VPN policies
    Affected if Interfaces are bound to VPN policies and dynamic interface configuration changes have been made recently
  5. Check for unauthenticated VPN access attempts
    Review VPN connection logs, authentication logs, and security event logs for any successful or attempted connections that bypassed normal authentication
    Affected if Evidence exists of VPN connections that succeeded without proper authentication or that bypassed configured VPN policies

A user is affected if they are running exactly version 6.2.2 of Cisco Secure Firewall Management Center with active VPN policies configured on the device.

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 vendor patch from Cisco for bug CSCvh49388 or upgrade to a fixed software version as specified in the Cisco security advisory.

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
12.0 hours of engineering $2,130
Get help mitigating

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

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