CVE-2013-0685
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 (WIS) 4.0 SP1SP1, 4.5- Portal, and 5.0- Portal does not restrict unspecified size and amount values, which allows remote attackers to execute arbitrary code or cause a denial of service (resource consumption) via unknown 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 confidenceInvensys Wonderware Information Server versions 4.0 SP1, 4.5-Portal, and 5.0-Portal contain a vulnerability where the application fails to properly validate or restrict size and amount values in unspecified input fields. This allows remote, unauthenticated attackers to send specially crafted requests that can trigger buffer overflow conditions leading to arbitrary code execution, or cause excessive resource consumption resulting in denial of service.
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.5= 5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Wonderware Information Server versionCheck the program's version through Windows Add/Remove Programs, the application's About dialog, or look for version information in the installation directory (typically C:\Program Files\Wonderware\Information Server\ or similar). The version may be displayed in the application itself or in installed component files.Affected if The installed version is 4.0 (particularly SP1), 4.5 (Portal variant), or 5.0 (Portal variant)
-
Confirm the specific build or patch levelLook for any installed service packs, patches, or updates. Check the application release notes or the Windows installed programs list for build numbers such as '4.0 SP1', '4.5-Portal', or '5.0-Portal'.Affected if The version shows as 4.0 SP1, 4.5-Portal, or 5.0-Portal specifically
-
Verify network exposure of the WIS serviceCheck if the Wonderware Information Server web interface or associated ports are accessible from untrusted networks. Identify the listening ports (typically HTTP/HTTPS on ports 80/443 or custom ports) and determine if firewall rules or network ACLs restrict access to authorized internal hosts only.Affected if The service is exposed to unauthenticated network access without proper firewall restrictions
-
Review access controls on the web interfaceExamine the IIS or built-in web server configuration for Wonderware Information Server. Check whether authentication is required for access and whether anonymous or unauthenticated requests are permitted to application endpoints.Affected if Anonymous or unauthenticated access is allowed to the application's web interface
-
Check for signs of exploitation attemptsReview web server logs, application logs, and Windows security event logs for unusual request patterns, especially those with abnormally large parameter values, repeated requests with unusual input, or indicators of buffer overflow attempts.Affected if Logs show suspicious requests with oversized input values or unusual patterns consistent with overflow attempts
You are affected if Wonderware Information Server version 4.0 (SP1), 4.5-Portal, or 5.0-Portal is installed AND the service is accessible to unauthenticated remote attackers on the network.
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 consider upgrading to a supported version of Wonderware Information Server, implementing network segmentation to restrict access to the WIS service, and placing the application behind a properly configured reverse proxy with input validation capabilities.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0685 — 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-2013-0685 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