CVE-2017-9957
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 · uneditedA vulnerability exists in Schneider Electric's U.motion Builder software versions 1.2.1 and prior in which the web service contains a hidden system account with a hardcoded password. An attacker can use this information to log into the system with high-privilege credentials.
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 confidenceSchneider Electric U.motion Builder versions 1.2.1 and prior contain a hidden system account with a hardcoded password embedded in the web service. This hardcoded credential provides high-privilege access and cannot be changed by administrators, allowing unauthenticated attackers to bypass authentication and gain administrative control of the system.
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<= 1.2.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 version of U.motion BuilderLocate the U.motion Builder installation and check the software version information. This is typically found in the application itself, its installation directory, or system information panels.Affected if The installed version is 1.2.1 or any earlier version.
-
Confirm web service component is activeDetermine whether the U.motion Builder web service is running and accessible on the network. Check if port 8080 or the default web service port is listening.Affected if The web service is exposed and the application version is 1.2.1 or prior.
-
Audit for unauthorized administrative accountsReview the list of user accounts in the U.motion Builder system, particularly looking for any unexpected or hidden accounts with administrative privileges that were not created by your administration team.Affected if An unknown high-privilege account exists that administrators did not create.
-
Review authentication logs for anomalous accessExamine web service and system authentication logs for successful logins from unusual sources, especially those occurring before normal administrative setup or outside expected business hours.Affected if Successful administrative access occurred from unknown sources or during periods when no legitimate administrators were using the system.
A system is affected if it runs Schneider Electric U.motion Builder version 1.2.1 or earlier and has the web service component exposed, as this version contains an exploitable hardcoded credential for a hidden administrative account.
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 dataIdentify and disable the hardcoded hidden account immediately, change all credentials, apply any available vendor patches, and consider network segmentation to limit exposure of the web service to trusted networks only.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9957 — 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-9957 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