dbcve.org
KingviewApplication · Wellintech

CVE-2011-4536

HIGH · 10.0 CVSS v2.0 Published 2011-12-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Heap-based buffer overflow in nettransdll.dll in HistorySvr.exe (aka HistoryServer.exe) in WellinTech KingView 6.53 and 65.30.2010.18018 allows remote attackers to execute arbitrary code via a crafted op-code 3 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 · high confidence

Heap-based buffer overflow in nettransdll.dll within HistorySvr.exe (HistoryServer) in WellinTech KingView versions 6.53 and 65.30.2010.18018 allows remote attackers to execute arbitrary code via specially crafted op-code 3 packets, exploiting insufficient bounds checking in heap memory allocation.

MitigationIsolate the KingView HistoryServer from untrusted networks and apply vendor-supplied patches when available; until a patch is released, restrict network access to the HistoryServer service via firewalls or network segmentation to prevent remote exploitation.

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
KingviewApplication
Affected:= 6.53= 65.30.2010.18018

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. Identify KingView installation and version
    Check the Windows registry under HKLM\SOFTWARE\WellinTech\KingView for the version value, or locate KingView installation directory (commonly C:\KingView) and check the version info of main executable files
    Affected if Installed version matches 6.53 or 65.30.2010.18018 exactly
  2. Locate HistorySvr.exe process
    Open Task Manager or use command 'tasklist /FI "IMAGENAME eq HistorySvr.exe"' to check if HistorySvr.exe is currently running
    Affected if HistorySvr.exe process is running on the system
  3. Verify nettransdll.dll presence
    Check the KingView installation directory (typically under C:\KingView\HistoryServer\) for the existence of nettransdll.dll
    Affected if nettransdll.dll file exists in the HistoryServer directory, indicating the vulnerable component is present
  4. Check network exposure of HistoryServer
    Use netstat command 'netstat -an | findstr :2001' (or check KingView documentation for default HistoryServer port) to see if the service is listening on network interfaces, and review firewall rules for inbound access to KingView ports
    Affected if HistoryServer is bound to non-loopback network interfaces and accepting remote connections

System is affected if KingView version 6.53 or 65.30.2010.18018 is installed with HistorySvr.exe running and accessible over 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
Patch available Apply the vendor patch
Vendor patch en.wellintech.com →
Interim mitigation

Isolate the KingView HistoryServer from untrusted networks and apply vendor-supplied patches when available; until a patch is released, restrict network access to the HistoryServer service via firewalls or network segmentation to prevent remote exploitation.

Recommended fix Moderate confidence
  1. Navigate to the vendor patch URL at http://en.wellintech.com/news/detail.aspx?contentid=166 to obtain the official vendor patch for this vulnerability
  2. Apply the vendor patch to the affected Kingview installation (versions 6.53 and 65.30.2010.18018) following the vendor's provided instructions
  3. After patching, verify that the nettransdll.dll component in HistorySvr.exe has been updated and the vulnerability is mitigated

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

Fix this in Kingview Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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