dbcve.org
Wonderware Archestra Configuration Access Component Activex ControlApplication · Invensys

CVE-2010-2974

HIGH · 9.3 CVSS v2.0 Published 2010-08-05
Fix available
A fix is available. Upgrade to after 3.1 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
Stack-based buffer overflow in the IConfigurationAccess interface in the Invensys Wonderware Archestra ConfigurationAccessComponent ActiveX control in Wonderware Application Server (WAS) before 3.1 SP2 P01, as used in the Wonderware Archestra Integrated Development Environment (IDE) and the InFusion Integrated Engineering Environment (IEE), allows remote attackers to execute arbitrary code via the first argument to the UnsubscribeData 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

Stack-based buffer overflow in the Wonderware Archestra ConfigurationAccessComponent ActiveX control's UnsubscribeData method allows remote attackers to execute arbitrary code via a crafted first argument. The vulnerability affects Wonderware Application Server versions before 3.1 SP2 P01, as well as the Archestra IDE and InFusion IEE.

MitigationUpdate Wonderware Application Server to version 3.1 SP2 P01 or later; alternatively, disable or unregister the vulnerable ActiveX control and implement network segmentation to restrict access to affected systems.

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
Wonderware Archestra Configuration Access Component Activex ControlApplication
Affected:all versions
Wonderware Application ServerApplication
Affected:<= 3.1= 2.0= 2.1= 3.0= 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
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 the ConfigurationAccessComponent ActiveX control
    Search the Windows registry for the CLSID of the ConfigurationAccessComponent ActiveX control under HKEY_CLASSES_ROOT, or check for DLL files related to Wonderware Archestra (such as ConfigurationAccessComponent.dll) in the Wonderware installation directory
    Affected if The ActiveX control DLL is present and registered on the system
  2. Verify Wonderware Application Server version
    Check the installed Wonderware Application Server version by looking in the Windows registry under the Wonderware product keys, or examine version information of the core server executables in the Wonderware installation folder
    Affected if The installed version is 2.0, 2.1, 3.0, or any 3.1 release (versions before 3.1 SP2 P01)
  3. Confirm ActiveX control is accessible from web contexts
    Check if Internet Explorer or other browsers can instantiate the ConfigurationAccessComponent ActiveX control by examining browser security settings, or look for the control in the list of installed ActiveX controls in Windows (manage add-ons in Internet Options)
    Affected if The ActiveX control is enabled and allowed to run in browser contexts

The system is affected if the Wonderware Archestra ConfigurationAccessComponent ActiveX control is present AND the Wonderware Application Server version is 3.1 or earlier (any version before 3.1 SP2 P01).

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

Update Wonderware Application Server to version 3.1 SP2 P01 or later; alternatively, disable or unregister the vulnerable ActiveX control and implement network segmentation to restrict access to affected systems.

Recommended fix High confidence

Wonderware Application Server 3.1 SP2 P01 or later

  1. 1. Identify the current version of Wonderware Application Server installed by checking the system information or the 'About' section in the Archestra IDE.
  2. 2. Confirm the installed version is vulnerable: versions prior to 3.1 SP2 P01, including 2.0, 2.1, 3.0, and 3.1 base.
  3. 3. Create a full backup of the current system, including all project files, configurations, and the SQL database if applicable.
  4. 4. Contact Wonderware/Invensys technical support or visit the official Wonderware customer portal to obtain the patched version 3.1 SP2 P01 or later.
  5. 5. Stop all Wonderware services and related runtime processes on the affected system before applying the patch.
  6. 6. Apply the upgrade following the vendor-provided installation instructions for version 3.1 SP2 P01.
  7. 7. After installation, restart Wonderware services and verify the Application Server starts successfully.
  8. 8. Test the IConfigurationAccess interface UnsubscribeData method functionality to confirm the vulnerability is patched and the control operates normally.
Caveat Upgrading major/minor versions of Wonderware Application Server may require compatibility checks with existing deployed applications, scripts, and third-party integrations; test thoroughly in a non-production environment first

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

Fix this in Wonderware Archestra Configuration Access Component Activex Control Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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