dbcve.org
U.motion BuilderApplication · Schneider Electric

CVE-2017-9956

HIGH · 7.3 CVSS v3.0 Published 2017-09-26
Fix available
A fix is available. Upgrade to after 1.2.1 or later.
See remediation →
82/100
Remediation priority · High
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
An authentication bypass vulnerability exists in Schneider Electric's U.motion Builder software versions 1.2.1 and prior in which the system contains a hard-coded valid session. An attacker can use that session ID as part of the HTTP cookie of a web request, resulting in authentication bypass

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

The U.motion Builder software versions 1.2.1 and prior contains a hard-coded valid session ID that can be used to bypass authentication. An attacker can simply include this pre-existing session identifier in the HTTP cookie of a web request to gain unauthorized access to the system without valid user credentials.

MitigationUpdate to a patched version of U.motion Builder that removes the hardcoded session. If no patch is available, implement proper dynamic session generation with cryptographically random session IDs and remove any static session credentials from the codebase.

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
U.motion BuilderApplication
Affected:<= 1.2.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed U.motion Builder version
    Locate the U.motion Builder installation directory and check the version information file, typically found in the software's about or help section, or check the installer metadata in the program files directory
    Affected if The installed version is 1.2.1 or any version number lower than 1.2.1
  2. Inspect application configuration files for hardcoded session identifiers
    Search configuration files within the U.motion Builder installation directory for static session tokens, session IDs, or cookie values that appear hardcoded rather than dynamically generated. Look in config.xml, web.config, or similar configuration files.
    Affected if Any configuration file contains a hardcoded session ID or static session token that remains constant across sessions or installations
  3. Examine the web application source or deployed files for static session credentials
    If you have access to the application's source code or deployed web files, search for strings resembling session identifiers, session tokens, or cookie values that are hardcoded as constants rather than generated at runtime
    Affected if Source code or deployed web files contain hardcoded session identifiers used for authentication bypass
  4. Review HTTP response headers and cookies for predictable session values
    Capture HTTP traffic between the client and U.motion Builder web interface using a proxy or packet capture tool. Examine Set-Cookie headers and session-related cookies for values that remain identical across fresh browser sessions or after logout/login cycles
    Affected if Session cookies or identifiers remain unchanged between different authentication attempts or after application restart

A user is affected if U.motion Builder version 1.2.1 or prior is installed, or if hardcoded session identifiers are found in configuration files, source code, or runtime traffic.

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 1.2.1
Interim mitigation

Update to a patched version of U.motion Builder that removes the hardcoded session. If no patch is available, implement proper dynamic session generation with cryptographically random session IDs and remove any static session credentials from the codebase.

Fix this in U.motion Builder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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