CVE-2017-9939
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 was discovered in Siemens SiPass integrated (All versions before V2.70) that could allow an attacker with network access to the SiPass integrated server to bypass the authentication mechanism and perform administrative operations.
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 confidenceSiemens SiPass integrated access control system versions before V2.70 contain an authentication bypass vulnerability. An attacker with network access to the SiPass integrated server can bypass the authentication mechanism and execute administrative operations, effectively gaining full control over the access control 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<= 2.65CVSS 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 SiPass integrated versionAccess the SiPass integrated server and check the installed version through the system administration interface, Windows Programs and Features, or the SiPass integrated About/Version information panelAffected if Installed version is 2.65 or earlier (any version <= 2.65)
-
Confirm server is network accessibleVerify network connectivity to the SiPass integrated server from untrusted networks by attempting to reach the server on typical SiPass ports (TCP ports used by the application for client-server communication)Affected if The SiPass server is reachable from networks outside the trusted management zone
You are affected if your SiPass integrated version is 2.65 or earlier AND the server is accessible from untrusted network segments, allowing remote attackers to bypass authentication and execute administrative operations.
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.
dbcve · scopedUpgrade SiPass integrated to version V2.70 or later. If immediate patching is not possible, restrict network access to the SiPass server using network segmentation and firewall rules to limit exposure to trusted sources only.
V2.70
- Backup the current SiPass Integrated system configuration and database
- Obtain the SiPass Integrated V2.70 update from Siemens (official vendor channels)
- Apply the V2.70 update following Siemens' documented upgrade procedure
- Verify the upgrade was successful by checking the version number
- Test that authentication is working properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation6.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9939 — 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-9939 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