dbcve.org
Sipass IntegratedApplication · Siemens

CVE-2017-9941

HIGH · 7.4 CVSS v3.0 Published 2017-08-08
Fix available
A fix is available. Upgrade to after 2.65 or later.
See remediation →
83/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
A vulnerability was discovered in Siemens SiPass integrated (All versions before V2.70) that could allow an attacker in a Man-in-the-Middle position between the SiPass integrated server and SiPass integrated clients to read or modify the network communication.

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

SiPass integrated versions before V2.70 have a Man-in-the-Middle vulnerability where network communication between the SiPass server and clients lacks proper encryption or authentication, allowing an attacker positioned on the network to intercept and potentially modify traffic.

MitigationUpgrade SiPass integrated to V2.70 or later, and ensure network segmentation restricts unauthorized MITM positioning.

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
Sipass IntegratedApplication
Affected:<= 2.65

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checks

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

  1. Identify SiPass Integrated version
    Open Windows Control Panel > Programs and Features, locate 'Siemens SiPass Integrated' and note the version number, or launch the SiPass application and check Help > About for the version
    Affected if version is 2.65 or earlier (any version displayed as 2.65 or lower)
  2. Compare version to affected range
    Compare your installed version against the affected range: any version <= 2.65 is vulnerable; versions 2.70 and later are not affected
    Affected if installed version number is 2.65 or any version below 2.70
  3. Confirm installation is genuine SiPass
    Verify the software is genuine Siemens SiPass Integrated (not a third-party access control system) by checking the vendor name in Programs and Features or the application splash screen
    Affected if software is Siemens SiPass Integrated version 2.65 or below

If the installed Siemens SiPass Integrated version is 2.65 or any version lower than 2.70, the environment is affected by this MITM vulnerability due to unencrypted network communication.

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

Upgrade SiPass integrated to V2.70 or later, and ensure network segmentation restricts unauthorized MITM positioning.

Fix this in Sipass Integrated Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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