dbcve.org
Ic3000 Industrial Compute Gateway FirmwareOperating system · Cisco

CVE-2019-12714

MEDIUM · 6.5 CVSS v3.1 Published 2019-10-02
Fix available
A fix is available. Upgrade to 1.1.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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-based management interface of Cisco IC3000 Industrial Compute Gateway could allow an authenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability exists because the affected software improperly manages system resources. An attacker could exploit this vulnerability by opening a large number of simultaneous sessions on the web-based management interface of an affected device. A successful exploit could allow the attacker to cause a DoS condition of the web-based management interface, preventing normal management operations.

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

The Cisco IC3000 Industrial Compute Gateway web-based management interface contains a resource management flaw where opening excessive simultaneous sessions depletes system resources, causing the web interface to become unavailable. An authenticated remote attacker can exploit this by establishing numerous concurrent connections.

MitigationApply Cisco firmware updates when available. In the interim, implement network-level rate limiting and connection throttling on external interfaces accessing the web management portal, and restrict management access to trusted IP ranges.

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
Ic3000 Industrial Compute Gateway FirmwareOperating system
Affected:< 1.1.1

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 device model is Cisco IC3000
    Access the device web interface or CLI and identify the hardware model. In the web UI, this is typically visible on the dashboard or in System > Device Information. Via CLI, use 'show version' or 'show inventory'.
    Affected if The device is NOT a Cisco IC3000 Industrial Compute Gateway (different models are not affected by this specific CVE).
  2. Check installed firmware version
    In the web UI, navigate to Administration > Firmware Upgrade or System > Device Information to view the current firmware version. Via CLI, use 'show version' and look for the firmware version number.
    Affected if The firmware version is below 1.1.1 (versions < 1.1.1 are vulnerable). Versions 1.1.1 and later contain the fix.
  3. Verify web management interface is enabled
    In the web UI, go to Administration > Management Access or System > HTTP/HTTPS Settings to confirm the web-based management interface is enabled.
    Affected if The web management interface is enabled and accessible (this is the attack vector for the vulnerability).
  4. Check for symptoms of resource exhaustion
    Monitor device availability and web UI responsiveness. Look for slow response times, timeouts, or inability to access the web interface. In CLI, use 'show processes cpu' or 'show memory' to check resource utilization.
    Affected if The device shows high CPU or memory usage, or the web interface is unresponsive or intermittently unavailable, which may indicate exploitation of this resource depletion flaw.

The device is affected if it is a Cisco IC3000 Industrial Compute Gateway running firmware version below 1.1.1 with the web management interface enabled and exposed.

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
Upgrade available Upgrade to 1.1.1 or later
Fixed in 1.1.1
Interim mitigation

Apply Cisco firmware updates when available. In the interim, implement network-level rate limiting and connection throttling on external interfaces accessing the web management portal, and restrict management access to trusted IP ranges.

Fix this in Ic3000 Industrial Compute Gateway Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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