dbcve.org
KinghistorianApplication · Wellintech

CVE-2012-2559

HIGH · 10.0 CVSS v2.0 Published 2012-07-05
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
WellinTech KingHistorian 3.0 allows remote attackers to execute arbitrary code or cause a denial of service (invalid pointer write) via a crafted packet to TCP port 5678.

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

WellinTech KingHistorian 3.0 contains a remote code execution vulnerability where crafted packets sent to TCP port 5678 cause an invalid pointer write, enabling attackers to execute arbitrary code or crash the service (DoS).

MitigationApply available vendor patches; if none exist, implement network segmentation to block unauthorized access to TCP port 5678, or upgrade to a newer version of KingHistorian if available.

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
KinghistorianApplication
Affected:= 3.0

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. Confirm KingHistorian is installed
    Look for KingHistorian installation in Program Files or check Windows services for 'KingHistorian' service
    Affected if KingHistorian software is present on the system
  2. Identify installed version
    Check the version of the KingHistorian executable (typically in the installation directory) by right-clicking the .exe file and selecting Properties, or using 'wmic product get name,version' if it was installed as a Windows installer
    Affected if Version reported is exactly 3.0
  3. Verify TCP port 5678 is listening
    Run 'netstat -an | findstr 5678' or use PowerShell 'Get-NetTCPConnection -LocalPort 5678' to check if the service is listening on port 5678
    Affected if Port 5678 is in LISTENING state and bound to a KingHistorian process
  4. Confirm KingHistorian service is running
    Check Windows Services console or run 'sc query KingHistorian' to see if the service is running
    Affected if KingHistorian service is currently running

System is affected if KingHistorian version 3.0 is installed, the service is running, and TCP port 5678 is actively listening (exposing the vulnerable service to network packets).

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 available vendor patches; if none exist, implement network segmentation to block unauthorized access to TCP port 5678, or upgrade to a newer version of KingHistorian if available.

Fix this in Kinghistorian Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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