CVE-2017-5155
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 · uneditedAn issue was discovered in Schneider Electric Wonderware Historian 2014 R2 SP1 P01 and earlier. Wonderware Historian creates logins with default passwords, which can allow a malicious entity to compromise Historian databases. In some installation scenarios, resources beyond those created by Wonderware Historian may be compromised as well.
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 confidenceWonderware Historian 2014 R2 SP1 P01 and earlier creates database login accounts with default passwords during installation. An attacker who obtains knowledge of these default credentials can authenticate to the Historian database and access stored operational data. In certain deployment configurations, the compromise may extend beyond the Historian system to other connected resources.
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= 2014_r2_sp1_p01CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 Historian versionCheck the product version through Windows Programs and Features, or look in the Wonderware installation directory for version information files (typically in C:\Program Files\Wonderware\Historian\ or C:\Program Files (x86)\Wonderware\Historian\). Look for version.txt, about.txt, or check the executable properties of the Historian main binaries.Affected if The installed version is 2014 R2 SP1 P01 or any version earlier than 2014 R2 SP1 P01.
-
Locate Historian database login accountsConnect to the underlying database (typically Microsoft SQL Server) used by Wonderware Historian. Access the SQL Server security logins or use the Historian Server Configuration utility to view configured database users. Look for service accounts and application-specific database users created during installation.Affected if Database login accounts exist that were created automatically by the Wonderware Historian installation process.
-
Verify default credential statusReview the Historian documentation or installation scripts to identify the expected default usernames and passwords. Check whether the database login accounts identified in step 2 are using these default credentials. This may require attempting to authenticate with known default credential pairs or reviewing password storage/configuration files if encryption is used.Affected if Any database login accounts are still configured with the factory-default passwords that were set during installation.
-
Assess account usage and exposureCheck SQL Server logs, Historian audit logs, or network logs for authentication attempts using the default accounts. Determine if these accounts are actively used by the Historian service or have been disabled. Review network access controls to assess whether these database accounts are accessible from network segments beyond the Historian server.Affected if Default accounts remain enabled, actively used by the Historian service, and accessible from network locations beyond the local server.
You are affected if Wonderware Historian 2014 R2 SP1 P01 or an earlier version is installed AND default database accounts created during installation still have their original default passwords configured.
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 dataChange all default passwords created by Wonderware Historian immediately. Disable unused default accounts, implement strong password policies, and apply network segmentation to limit exposure from compromised credentials.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5155 — 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-2017-5155 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