CVE-2015-3962
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 · uneditedSchneider Electric StruxureWare Building Expert MPM before 2.15 does not use encryption for the client-server data stream, which allows remote attackers to discover credentials by sniffing the network.
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 StruxureWare Building Expert MPM versions prior to 2.15 transmit client-server communication in plaintext without encryption, allowing remote attackers on the same network segment to capture credentials by sniffing network traffic.
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< 2.15CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if StruxureWare Building Expert MPM is installedLocate the Schneider Electric StruxureWare Building Expert installation directory, typically found under Program Files or Program Files (x86), or check the Windows Add/Remove Programs list for 'StruxureWare Building Expert Multi Purpose Management'Affected if The software is present on the system
-
Determine the installed versionOpen the application's About or Help section, or check the version property of the executable file in the installation directoryAffected if The version cannot be determined or is below 2.15
-
Compare version against affected rangeReview the identified version number and compare it to the threshold of 2.15Affected if The installed version is any version prior to 2.15 (e.g., 2.14, 2.10, 1.x)
-
Verify plaintext credential transmissionUse a network packet capture tool (such as Wireshark or tcpdump) on the network segment to capture outgoing traffic from the MPM client to server and inspect whether credentials are transmitted in cleartext rather than encryptedAffected if Network traffic analysis reveals plaintext username/password fields in client-server communication
The environment is affected if Schneider Electric StruxureWare Building Expert MPM version is installed and that version is prior to 2.15, with credentials being transmitted unencrypted on the network.
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 data2.15
Upgrade to version 2.15 or later which implements encryption for the client-server data stream. If immediate upgrade is not feasible, implement network segmentation and restrict physical/logical access to the network segment housing the MPM system.
- Consultation3.0 h
- Implementation4.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3962 — 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-2015-3962 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