CVE-2015-5717
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 · uneditedThe Siemens COMPAS Mobile application before 1.6 for Android does not properly verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
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 confidenceThe Siemens COMPAS Mobile application before version 1.6 for Android fails to properly validate X.509 certificates from SSL servers. This allows man-in-the-middle attackers to intercept encrypted communications by presenting crafted fraudulent certificates, enabling server spoofing and theft of sensitive data transmitted through the app.
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.5CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/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.
-
Verify Siemens COMPAS Mobile is installedOpen the Android device Settings, go to Apps or Applications, and search for 'COMPAS' or 'Siemens COMPAS Mobile' in the installed applications listAffected if The application appears in the installed apps list
-
Determine the installed versionIn the app settings screen (Settings > Apps > COMPAS Mobile), locate the 'Version' or 'Version info' field displayed under the app nameAffected if A version number is displayed in the app info
-
Compare version against affected rangeCheck if the displayed version number is 1.5 or lower (for example: 1.5, 1.4, 1.3, etc.)Affected if Version is 1.5 or earlier (the app is vulnerable)
-
Verify certificate validation behavior (optional)Since this is a mobile app, network traffic inspection or penetration testing tools could be used on a test environment to confirm improper certificate validation occurs during SSL/TLS connectionsAffected if The app accepts fraudulent certificates during SSL/TLS handshake
The environment is affected if Siemens COMPAS Mobile for Android is installed with version 1.5 or earlier, as these versions fail to properly validate X.509 certificates.
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 dataUpgrade Siemens COMPAS Mobile to version 1.6 or later which includes proper X.509 certificate validation. Until upgraded, avoid using the application on untrusted networks such as public Wi-Fi.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5717 — 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-5717 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