dbcve.org
KingscadaApplication · Wellintech

CVE-2014-0787

HIGH · 10.0 CVSS v2.0 Published 2014-04-12
Fix available
A fix is available. Upgrade to after 3.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Stack-based buffer overflow in WellinTech KingSCADA before 3.1.2.13 allows remote attackers to execute arbitrary code via a crafted packet.

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 stack-based buffer overflow vulnerability exists in WellinTech KingSCADA versions prior to 3.1.2.13. The vulnerability is triggered during packet parsing, allowing remote attackers to overflow a stack buffer and execute arbitrary code by sending a specially crafted packet to the affected SCADA server.

MitigationUpgrade KingSCADA to version 3.1.2.13 or later. Additionally, network segmentation and firewall rules should restrict unauthorized access to SCADA management ports.

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
KingscadaApplication
Affected:<= 3.1.2= 3.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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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. Locate KingSCADA installation directory
    Check common installation paths: C:\Program Files\WellinTech\KingSCADA, C:\KingSCADA, or search for 'KingSCADA.exe' on the system. Also check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for KingSCADA entries.
    Affected if KingSCADA software is found on the system
  2. Identify installed KingSCADA version
    Once the installation directory is found, check the version of KingSCADA.exe or KingScada.exe (file name may vary). Right-click the executable, select Properties, and view the Details tab for Product Version. Alternatively, check the version in the Windows Registry key HKLM\SOFTWARE\WellinTech\KingSCADA\Version if it exists.
    Affected if Version is 3.1, 3.1.1, 3.1.2, or any version prior to 3.1.2.13 (the product version shows a number lower than 3.1.2.13)
  3. Verify SCADA server service is running
    Open Services (services.msc) and look for KingSCADA-related services such as 'KingSCADA Server' or 'KingSCADA Runtime'. Also check Task Manager for running KingSCADA processes.
    Affected if The KingSCADA server or runtime service is actively running, exposing the vulnerable packet parsing code to network traffic

A system is affected if WellinTech KingSCADA is installed with version 3.1 through 3.1.2 (or any version prior to 3.1.2.13) and the SCADA server component is running and accessible on the network.

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
Upgrade available Upgrade to a release after 3.1.2
Interim mitigation

Upgrade KingSCADA to version 3.1.2.13 or later. Additionally, network segmentation and firewall rules should restrict unauthorized access to SCADA management ports.

Recommended fix High confidence

KingSCADA 3.1.2.13 or later

  1. 1. Back up the current KingSCADA project and configuration files
  2. 2. Download KingSCADA version 3.1.2.13 or later from the official WellinTech website
  3. 3. Verify the integrity of the downloaded installer using checksums if provided
  4. 4. Stop all KingSCADA services and related processes on the server
  5. 5. Install the new version following the vendor's installation documentation
  6. 6. Restore the backed-up project files to the upgraded system
  7. 7. Start KingSCADA services and verify proper operation
  8. 8. Test critical functions in a non-production environment before deploying to production
Caveat SCADA systems may require regression testing of control logic after upgrade; ensure compatibility with connected PLCs and field devices

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

Fix this in Kingscada Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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