dbcve.org
ProviewApplication · Eaton

CVE-2014-9196

HIGH · 9.3 CVSS v2.0 Published 2015-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Eaton Cooper Power Systems ProView 4.0 and 5.0 before 5.0 11 on Form 6 controls and Idea and IdeaPLUS relays generates TCP initial sequence number (ISN) values linearly, which makes it easier for remote attackers to spoof TCP sessions by predicting an ISN value.

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

The ProView 4.0 and 5.0 SCADA control devices and Idea/IdeaPLUS relays implement a flawed TCP Initial Sequence Number (ISN) generation algorithm that produces predictable, linearly-incrementing values. Attackers can sniff traffic and accurately predict the next ISN, enabling TCP session hijacking and injection attacks against these critical power grid protection devices.

MitigationApply vendor-supplied firmware updates (ProView 5.0.11 or later) to remediate the predictable ISN vulnerability; if patches are unavailable, isolate affected devices behind strict network segmentation with deep packet inspection to detect TCP spoofing 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
ProviewApplication
Affected:= 4.0= 5.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7= 5.0.8= 5.0.9= 5.0.10

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 ProView device on the network
    Review network asset inventory or use network scanning tools to locate devices running ProView SCADA software. Check device hostname, web interface, or SNMP sysDescr for 'ProView' or 'Eaton' identifiers.
    Affected if A ProView device is found on the network with any IP address in your asset inventory.
  2. Determine ProView firmware version
    Access the ProView device web interface (typically via HTTP/HTTPS on port 80/443) and navigate to the System Information or About page to retrieve the firmware version. Alternatively, query the device via SNMP using the sysDescr OID (1.3.6.1.2.1.1.1).
    Affected if The firmware version displayed is 4.0, 5.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, or 5.0.10.
  3. Verify version against affected range
    Compare the installed firmware version to the known affected versions: 4.0, 5.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, or 5.0.10. Any exact match indicates the device is vulnerable.
    Affected if The installed version exactly matches any version in the list 4.0 through 5.0.10.
  4. Confirm TCP service is exposed
    Check if the ProView device has TCP services enabled (such as Modbus/TCP, DNP3, or proprietary SCADA protocols) by reviewing firewall rules or performing a TCP port scan (common ports: 502, 20000, 80, 443).
    Affected if The ProView device has accessible TCP services and responds to network connections.

A user is affected if an Eaton ProView device with firmware version 4.0 through 5.0.10 is present on the network with TCP services 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates (ProView 5.0.11 or later) to remediate the predictable ISN vulnerability; if patches are unavailable, isolate affected devices behind strict network segmentation with deep packet inspection to detect TCP spoofing attempts.

Recommended fix High confidence

ProView 5.0.11 or later

  1. Identify the current ProView version installed on the Form 6 controls or Idea/IdeaPLUS relays
  2. Contact Eaton Technical Support to obtain ProView version 5.0.11 or later
  3. Upgrade ProView software to version 5.0.11 or newer following the vendor's upgrade procedure
  4. After upgrade, verify the TCP ISN generation behavior has been corrected
  5. Confirm the new ProView version is displayed correctly in the system information
Caveat As this is an ICS/industrial control system, conduct thorough testing in a staging environment before production deployment to ensure compatibility with connected devices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Proview Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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