Foxboro Control SoftwareApplication · Invensys

CVE-2012-3005

MEDIUM · 6.9 CVSS v2.0 Published 2012-07-26
Fix available
A fix is available. Upgrade to after 2012 or later.
See remediation →
74/100
Remediation priority · Elevated
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
Untrusted search path vulnerability in Invensys Wonderware InTouch 2012 and earlier, as used in Wonderware Application Server, Wonderware Information Server, Foxboro Control Software, InFusion CE/FE/SCADA, InBatch, and Wonderware Historian, allows local users to gain privileges via a Trojan horse DLL in an unspecified directory.

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

Untrusted search path vulnerability allows local users to place a malicious DLL in an unspecified directory that Wonderware InTouch 2012 and related products load from, resulting in privilege escalation. The application searches directories in an insecure order, allowing DLL preloading attacks.

MitigationApply vendor patches for InTouch 2012 and related Wonderware products. Ensure installation directories are not writable by unprivileged users and remove any suspicious DLLs from the search path.

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
Foxboro Control SoftwareApplication
Affected:= 3.1= 4.0
Infusion Ce\/fe\/scadaApplication
Affected:<= 2.5
IntouchApplication
Affected:<= 2012
Intouch\/wonderware Application ServerApplication
Affected:<= 2012= 10.0= 10.5
Wonderware HistorianApplication
Affected:<= 10.0= 10.0
Wonderware InbatchApplication
Affected:<= 9.5
Wonderware Information ServerApplication
Affected:<= 4.5= 3.1= 4.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
Local
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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. Identify installed Wonderware/Invensys product versions
    Use the system's software inventory or check the program's About/Version information to determine the exact version of any Wonderware, Invensys Foxboro, Invensys Infusion, or related products installed.
    Affected if The installed version matches one of the affected ranges: Foxboro Control Software 3.1 or 4.0; Infusion Ce/fe/scada versions 2.5 or lower; InTouch versions 2012 or lower; Application Server versions 2012, 10.0, or 10.5; Historian versions 10.0 or lower; Inbatch versions 9.5 or lower; Information Ser
  2. Identify the application's working directory
    Locate the installation directory of the Wonderware/InTouch application by reviewing the shortcut properties or searching for the main executable such as intouch.exe or related binaries.
    Affected if The working directory is writable by non-privileged users, allowing them to place a malicious DLL file.
  3. Review DLL search path order
    Examine how the application loads DLLs by monitoring it with process monitoring tools or checking the application's configuration for DLL loading behavior.
    Affected if The application loads DLLs from the current working directory or other user-writable locations before checking system directories, enabling DLL preloading attacks.
  4. Inspect for unexpected DLLs in application directories
    List all DLL files in the application's installation directory and any directories in its search path, looking for unfamiliar or recently added DLLs.
    Affected if Suspicious or unexpected DLL files exist in directories the application uses, indicating potential exploitation.

A user is affected if they have any of the listed vulnerable product versions installed and the application runs with elevated privileges while allowing writable directories in its DLL search path.

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

Apply vendor patches for InTouch 2012 and related Wonderware products. Ensure installation directories are not writable by unprivileged users and remove any suspicious DLLs from the search path.

Fix this in Foxboro Control Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-3005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-3005 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