dbcve.org
Advantech StudioApplication · Advantech

CVE-2011-0340

HIGH · 9.3 CVSS v2.0 Published 2011-05-04
Fix available
A fix is available. Upgrade to after 7.0 or later.
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
Multiple buffer overflows in the ISSymbol ActiveX control in ISSymbol.ocx 61.6.0.0 and 301.1009.2904.0 in the ISSymbol virtual machine, as distributed in Advantech Studio 6.1 SP6 61.6.01.05, InduSoft Web Studio before 7.0+SP1, and InduSoft Thin Client 7.0, allow remote attackers to execute arbitrary code via a long (1) InternationalOrder, (2) InternationalSeparator, or (3) LogFileName property value; or (4) a long bstrFileName argument to the OpenScreen method.

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

Multiple buffer overflow vulnerabilities exist in the ISSymbol ActiveX control (ISSymbol.ocx) versions 61.6.0.0 and 301.1009.2904.0, as used in Advantech Studio and InduSoft Web Studio. The overflows occur when overly long strings are passed to the InternationalOrder, InternationalSeparator, or LogFileName properties, or to the OpenScreen method's bstrFileName parameter, allowing remote attackers to execute arbitrary code.

MitigationUpdate to InduSoft Web Studio 7.0+SP1 or later which contains the patched ISSymbol.ocx control. If immediate patching is not feasible, disable the ISSymbol ActiveX control in Internet Explorer or deploy the Microsoft 'Kill Bit' for this ActiveX control to prevent it from loading.

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
Advantech StudioApplication
Affected:= 6.1
Thin ClientApplication
Affected:= 7.0
Web StudioApplication
Affected:<= 7.0= 6.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
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. Locate ISSymbol.ocx on the system
    Search for ISSymbol.ocx file on the system. Check the Windows System32 directory (C:\Windows\System32\) and product installation directories (typically under C:\Program Files\Advantech or C:\Program Files\InduSoft). Use the command: dir /s C:\ISSymbol.ocx or Windows Search.
    Affected if If the ISSymbol.ocx file exists on the system, the vulnerable ActiveX control is present.
  2. Check ISSymbol.ocx file version
    Right-click on the ISSymbol.ocx file, select Properties, then view the File Version on the Details tab. Alternatively, use PowerShell: (Get-Item 'C:\Windows\System32\ISSymbol.ocx').VersionInfo.FileVersion
    Affected if If the file version is 61.6.0.0 or 301.1009.2904.0, the control is a known vulnerable version.
  3. Check installed product versions
    Open Add or Remove Programs (appwiz.cpl) or check the product installation directories for Advantech Studio or InduSoft Web Studio. Identify the exact version number of the installed application.
    Affected if If Advantech Studio version 6.1, InduSoft Web Studio version 6.1 or <=7.0, or Induft Thin Client version 7.0 is installed, the vulnerable ISSymbol.ocx control may be present.
  4. Verify ActiveX control is registered
    Search the Windows Registry for ISSymbol.ocx under HKCR\CLSID or HKLM\SOFTWARE\Microsoft\Code Store Database\SKUInstallations. Use regedit or PowerShell: Get-ChildItem -Path 'HKLM:\SOFTWARE\Microsoft\Code Store Database\SKUInstallations' -Recurse -ErrorAction SilentlyContinue
    Affected if If the control is registered in the registry, it can be instantiated by Internet Explorer or other applications, making the vulnerability exploitable.

A system is affected if ISSymbol.ocx version 61.6.0.0 or 301.1009.2904.0 is present, or if any of the affected products (Advantech Studio 6.1, InduSoft Web Studio 6.1/7.0, or InduSoft Thin Client 7.0) are installed with the vulnerable control registered and available for use.

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 7.0
Interim mitigation

Update to InduSoft Web Studio 7.0+SP1 or later which contains the patched ISSymbol.ocx control. If immediate patching is not feasible, disable the ISSymbol ActiveX control in Internet Explorer or deploy the Microsoft 'Kill Bit' for this ActiveX control to prevent it from loading.

Recommended fix Moderate confidence

InduSoft Web Studio 7.0 SP1 or later; Advantech Studio 6.1 SP6 patch or subsequent version; InduSoft Thin Client 7.0 patch or subsequent version

  1. Identify the specific InduSoft/Advantech product installed (Advantech Studio, InduSoft Web Studio, or InduSoft Thin Client)
  2. For InduSoft Web Studio: Upgrade to version 7.0 SP1 or later to remediate the buffer overflow vulnerability in ISSymbol.ocx
  3. For Advantech Studio 6.1: Contact Advantech support for the specific patch or upgrade path to a fixed version
  4. For InduSoft Thin Client 7.0: Contact Advantech/InduSoft for the specific patch or upgrade to a fixed version
  5. Verify the ISSymbol.ocx version after upgrade to confirm the fix (versions prior to 61.6.0.0 or 301.1009.2904.0 should be replaced)
  6. If upgrading is not immediately possible, disable the ISSymbol ActiveX control in Internet Explorer by setting the kill bit for the clsid {2D4B2440-863D-11D1-9DAB-006008166E7C}
Caveat Review release notes for Web Studio 7.0 SP1 for any compatibility changes with existing projects; test thoroughly in a non-production environment before deploying

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

Fix this in Advantech Studio Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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