CVE-2012-3007
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 · uneditedStack-based buffer overflow in slssvc.exe before 58.x in Invensys Wonderware SuiteLink in the Invensys System Platform software suite, as used in InTouch/Wonderware Application Server IT before 10.5 and WAS before 3.5, DASABCIP before 4.1 SP2, DASSiDirect before 3.0, DAServer Runtime Components before 3.0 SP2, and other products, allows remote attackers to cause a denial of service (daemon crash or hang) via a long Unicode string.
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 confidenceStack-based buffer overflow vulnerability in the slssvc.exe service (Wonderware SuiteLink) prior to version 58.x. The overflow is triggered by sending a long Unicode string to the service, causing a denial of service via daemon crash or hang. This affects multiple Invensys Wonderware products used in industrial control system environments.
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<= 4.1= 4.1<= 3.0= 3.0<= 2.0<= 10.0<= 3.1= 3.0= 3.0.200= 3.1= 3.1.201CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the slssvc.exe service fileSearch the system for slssvc.exe, typically found in Wonderware installation directories such as C:\Program Files\Wonderware\ or C:\Wonderware\. Use File Explorer search or command: dir /s C:\slssvc.exeAffected if The file exists on the system, indicating SuiteLink is installed
-
Check the version of slssvc.exeRight-click slssvc.exe, select Properties, then go to the Details tab to view the File Version. Compare this version number to 58.x. Versions prior to 58.x are vulnerable.Affected if The file version is below 58.x (for example, 57.x, 56.x, or any version number less than 58)
-
Verify if SuiteLink service is runningOpen Services console (services.msc) and look for a service named 'Wonderware SuiteLink' or 'SuiteLink'. Alternatively, run command: sc queryex type= service state= all | findstr /i "slssvc"Affected if The service is installed and running, exposing the vulnerability to network attackers
-
Identify installed Wonderware products and versionsCheck Windows Programs and Features (appwiz.cpl) for installed Wonderware products such as DASABCIP, DASServer, DASSiDirect, Intouch, or Wonderware Application Server. Note their version numbers.Affected if Any of these products are installed with versions matching the affected ranges: DASABCIP <= 4.1, DASServer <= 3.0, DASSiDirect <= 2.0, Intouch/Wonderware Application Server <= 10.0, or Wonderware Application Server <= 3.1
A system is affected if slssvc.exe version is below 58.x AND the SuiteLink service is running, particularly when combined with any of the listed vulnerable Wonderware product versions installed on the same system.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches to upgrade slssvc.exe to version 58.x or later, and update affected Wonderware components to the specified fixed versions (IT 10.5+, WAS 3.5+, DASABCIP 4.1 SP2+, DASSiDirect 3.0+, DAServer Runtime 3.0 SP2+). Implement network segmentation to limit exposure of SuiteLink services to untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3007 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3007 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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