CVE-2012-3847
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 · uneditedslssvc.exe in Invensys Wonderware SuiteLink in Invensys InTouch 2012 and Wonderware Application Server 2012 allows remote attackers to cause a denial of service (resource consumption) via a long Unicode string, a different vulnerability than CVE-2012-3007.
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 confidenceThe slssvc.exe service in Invensys Wonderware SuiteLink (part of InTouch 2012 and Wonderware Application Server 2012) is vulnerable to remote denial of service via specially crafted network packets containing excessively long Unicode strings, causing resource exhaustion.
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= 2012= 2012CVSS 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.
-
Verify InTouch 2012 or Wonderware Application Server 2012 installationCheck the Windows registry at HKLM\SOFTWARE\Wonderware or look for Wonderware installation folders (typically C:\Program Files\Wonderware or C:\ArchestrA). Use 'Get-ItemProperty' or inspect Add/Remove Programs for these products with version 2012.Affected if Either InTouch 2012 or Wonderware Application Server 2012 is installed on the system.
-
Locate the slssvc.exe service executableSearch for slssvc.exe in the Wonderware installation directory, commonly found in C:\Program Files\Wonderware\Common or C:\ArchestrA\Framework. Use 'Get-ChildItem -Recurse' or file explorer to locate the file.Affected if The slssvc.exe file exists on the system.
-
Determine if the SuiteLink service is runningOpen Windows Services (services.msc) and look for 'Wonderware SuiteLink' or check via command line with 'sc query slssvc' or 'Get-Service -Name *SuiteLink*'. Also check running processes for slssvc.exe in Task Manager.Affected if The slssvc.exe service is currently running.
-
Check network exposure of the SuiteLink serviceVerify if the SuiteLink port (default TCP 20000) is listening and accessible. Use 'netstat -an | findstr 20000' or check firewall rules. Determine if the service is bound to non-loopback interfaces accessible from the network.Affected if The SuiteLink service is listening on a network-accessible interface (0.0.0.0 or external IP) rather than localhost only.
The environment is affected if InTouch 2012 or Wonderware Application Server 2012 is installed with the slssvc.exe service running and exposed to network traffic.
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 if available; otherwise isolate the affected service behind firewalls or disable SuiteLink if not required for operations.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3847 — 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-3847 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