Wonderware Intouch Access Anywhere ServerApplication · Schneider Electric

CVE-2014-9190

HIGH · 10.0 CVSS v2.0 Published 2015-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Stack-based buffer overflow in Schneider Electric Wonderware InTouch Access Anywhere Server 10.6 and 11.0 allows remote attackers to execute arbitrary code via a request for a filename that does not exist.

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 confidence

Stack-based buffer overflow in Schneider Electric Wonderware InTouch Access Anywhere Server versions 10.6 and 11.0 allows remote attackers to execute arbitrary code via crafted HTTP requests for non-existent files.

MitigationApply vendor security patches or upgrade to a fixed version of InTouch Access Anywhere Server; until patched, restrict network exposure of the server and monitor for exploitation attempts.

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
Wonderware Intouch Access Anywhere ServerApplication
Affected:= 10.6= 11.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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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. Verify InTouch Access Anywhere Server is installed
    Check for the presence of the Wonderware InTouch Access Anywhere Server service or application installation on the system. Look for the service named 'Wonderware InTouch Access Anywhere' or check Program Files for Wonderware directories.
    Affected if The product is installed on the system
  2. Identify the installed version
    Locate the version information for the installed InTouch Access Anywhere Server. Check the application's About section, the Windows installed programs list, or any version file within the installation directory.
    Affected if The installed version equals 10.6 or 11.0 exactly
  3. Confirm HTTP service is listening
    Check if the InTouch Access Anywhere Server HTTP service is running and listening on its configured port (typically port 80 or 443). Use netstat or similar tool to verify the service is bound to a network interface.
    Affected if The HTTP service is active and listening on a network-facing interface
  4. Assess network exposure
    Determine if the server is accessible from outside the local network by reviewing firewall rules, network configurations, and any port forwarding settings that expose the HTTP service.
    Affected if The server HTTP port is accessible from untrusted networks or the internet
  5. Inspect HTTP access logs for anomalous requests
    Review the InTouch Access Anywhere Server HTTP access logs for requests to non-existent files or directories, particularly those with unusually long URL paths that may indicate exploitation attempts.
    Affected if Logs show requests to non-existent resources with abnormal patterns or evidence of buffer overflow attempts

The environment is affected if Schneider Electric Wonderware InTouch Access Anywhere Server version 10.6 or 11.0 is installed with its HTTP service exposed to the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor security patches or upgrade to a fixed version of InTouch Access Anywhere Server; until patched, restrict network exposure of the server and monitor for exploitation attempts.

Fix this in Wonderware Intouch Access Anywhere Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-9190 — 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-2014-9190 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