dbcve.org
Wonderware Intouch Access AnywhereApplication · Aveva

CVE-2017-5160

MEDIUM · 5.3 CVSS v3.1 Published 2017-04-20
Fix available
A fix is available. Upgrade to after 11.5.2 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
An Inadequate Encryption Strength issue was discovered in Schneider Electric Wonderware InTouch Access Anywhere, version 11.5.2 and prior. The software will connect via Transport Layer Security without verifying the peer's SSL certificate properly.

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

Schneider Electric Wonderware InTouch Access Anywhere version 11.5.2 and prior uses Transport Layer Security (TLS) for connections but fails to properly verify the peer's SSL certificate, allowing an attacker to perform man-in-the-middle attacks by presenting a fraudulent certificate.

MitigationImplement proper SSL/TLS certificate validation to verify the certificate chain, hostname, and revocation status before establishing the connection, or configure the application to use certificate pinning for trusted endpoints.

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 AnywhereApplication
Affected:<= 11.5.2

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Identify installed version of Wonderware InTouch Access Anywhere
    Open Windows Control Panel, go to Programs and Features, or check the installation directory for version information. Look for 'Wonderware InTouch Access Anywhere' in the installed programs list and note the version number shown.
    Affected if The installed version is 11.5.2 or any earlier version (e.g., 11.5, 11.0, 10.x)
  2. Check the Windows service for InTouch Access Anywhere
    Open Services (services.msc), locate the 'Wonderware InTouch Access Anywhere' or 'Access Anywhere' service, right-click and select Properties to view the service name, status, and executable path.
    Affected if The service exists and is running on a system with version 11.5.2 or prior
  3. Locate the Access Anywhere installation directory
    Navigate to the default installation path, typically C:\Program Files\Wonderware\InTouchAccessAnywhere\ or check the executable path from the Windows service properties to find the installation folder.
    Affected if The software is installed in a directory matching the affected product path
  4. Identify SSL/TLS configuration settings
    Examine the configuration files in the installation directory, particularly any XML, INI, or config files related to server settings, web server configuration, or SSL/TLS settings. Look for parameters controlling certificate validation.
    Affected if Configuration files exist and contain SSL/TLS settings, particularly if certificate validation is disabled or not properly configured
  5. Test SSL certificate validation behavior
    Use a web browser to connect to the Access Anywhere web interface over HTTPS. Observe whether the browser shows certificate warnings or errors. Note: This is informational and may indicate the presence of the vulnerability if no proper certificate validation occurs.
    Affected if The web interface accepts connections without proper certificate chain validation

A system is affected if Wonderware InTouch Access Anywhere version 11.5.2 or earlier is installed and the SSL/TLS server component is enabled, allowing potential man-in-the-middle attacks due to improper certificate verification.

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
Upgrade available Upgrade to a release after 11.5.2
Interim mitigation

Implement proper SSL/TLS certificate validation to verify the certificate chain, hostname, and revocation status before establishing the connection, or configure the application to use certificate pinning for trusted endpoints.

Fix this in Wonderware Intouch Access Anywhere Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5160 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2017-5160 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