dbcve.org
Firepower Extensible Operating SystemOperating system · Cisco

CVE-2017-12299

MEDIUM · 5.3 CVSS v3.0 Published 2017-11-16
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 exists in the process of creating default IP blocks during device initialization for Cisco ASA Next-Generation Firewall Services that could allow an unauthenticated, remote attacker to send traffic to the local IP address of the device, bypassing any filters that are configured to deny local IP management traffic. The vulnerability is due to an implementation error that exists in the process of creating default IP blocks when the device is initialized, and the way in which those IP blocks interact with user-configured filters for local IP management traffic (for example, SSH to the device). An attacker could exploit this vulnerability by sending traffic to the local IP address of the targeted device. A successful exploit could allow the attacker to connect to the local IP address of the device even when there are filters configured to deny the traffic. Cisco Bug IDs: CSCvd97962.

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 ASA Next-Generation Firewall Services allows unauthenticated remote attackers to bypass configured filters for local IP management traffic (e.g., SSH). The flaw exists in the implementation error during the process of creating default IP blocks when the device initializes. Attackers can exploit this by sending traffic directly to the device's local IP address, bypassing user-configured management access controls.

MitigationApply the Cisco fix for bug CSCvd97962 (software update). Until patched, implement additional network-level controls to restrict access to the device's local IP addresses and monitor for unauthorized management access attempts.

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
Firepower Extensible Operating SystemOperating system
Affected:= 2.2\(1.58\)

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.0/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. Identify Cisco FXOS installation
    Confirm the device runs Cisco Firepower Extensible Operating System (FXOS). On the ASA CLI, use 'show version' to identify the operating system. Look for 'Cisco Firepower Extensible Operating System' or 'FXOS' in the output.
    Affected if the device runs Cisco Firepower Extensible Operating System
  2. Check the FXOS version number
    On the ASA CLI, use 'show version' and locate the FXOS version. The vulnerable version is exactly 2.2(1.58). Compare your installed version against this specific release.
    Affected if the installed FXOS version is exactly 2.2(1.58)
  3. Verify management access configuration
    Check if the device has management access configured for local IP addresses. Use 'show running-config | include management-access' to see if a management interface is defined. Then use 'show running-config' to review any 'management-access' or 'http'/'ssh' commands that apply to the device's local IP addresses.
    Affected if management access (SSH, HTTP, HTTPS) is configured on the device's local IP addresses

the device is affected if it runs Cisco FXOS version 2.2(1.58) and has management access enabled on local IP addresses, allowing attackers to bypass configured management access controls

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 fix for bug CSCvd97962 (software update). Until patched, implement additional network-level controls to restrict access to the device's local IP addresses and monitor for unauthorized management access attempts.

Fix this in Firepower Extensible Operating System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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