CVE-2012-0228
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 · uneditedInvensys Wonderware Information Server 4.0 SP1 and 4.5 does not properly implement client controls, which allows remote attackers to bypass intended access restrictions via unspecified vectors.
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 Invensys Wonderware Information Server versions 4.0 SP1 and 4.5 fail to properly enforce client-side access controls, allowing remote attackers to bypass intended security restrictions through unspecified attack vectors. This appears to be a missing or insufficient authentication/authorization check that should be performed server-side but can be circumvented.
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.0= 4.5CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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 Wonderware Information Server is installedCheck for Wonderware Information Server installation on the target system by looking for the product in installed programs or checking for its installation directory (typically under the Invensys or Wonderware program folder).Affected if The software is present on the system.
-
Determine the installed versionLocate and read the version information for Wonderware Information Server. This is typically available in the product itself, installation directory, or system registry. Compare the exact version number to the affected versions 4.0 and 4.5.Affected if The installed version equals 4.0 or 4.5 specifically.
-
Confirm the service is running and accessibleVerify that the Wonderware Information Server service is running and network-accessible. Check if the relevant ports (typically TCP ports used by IIS or the application server) are listening and exposed.Affected if The server is running and network-accessible, making the access control bypass exploitable remotely.
-
Identify network exposureReview firewall rules and network configuration to determine if the server is directly accessible from untrusted networks. Determine whether the server is behind proper network segmentation.Affected if The server is exposed to untrusted networks without adequate network-level filtering.
The environment is affected if Wonderware Information Server version 4.0 or 4.5 is installed and the server is network-accessible, allowing remote attackers to bypass client-side access controls.
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 any available vendor patches for Wonderware Information Server; if no patch exists, implement compensating controls such as network segmentation and strict firewall rules to limit exposure to trusted networks only.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0228 — 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-0228 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