dbcve.org
Sipass IntegratedApplication · Siemens

CVE-2022-31810

HIGH · 7.5 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 2.90.3.8 or later.
See remediation →
84/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 has been identified in SiPass integrated (All versions < V2.90.3.8). Affected server applications improperly check the size of data packets received for the configuration client login, causing a stack-based buffer overflow. This could allow an unauthenticated remote attacker to crash the server application, creating a denial of service condition.

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

A stack-based buffer overflow vulnerability exists in SiPass integrated server applications (all versions < V2.90.3.8). The server improperly validates the size of data packets received during configuration client login, allowing an attacker to overflow a stack-based buffer. This enables an unauthenticated remote attacker to crash the server application, creating a denial of service condition.

MitigationUpgrade SiPass integrated to version V2.90.3.8 or later to patch the vulnerability. If immediate upgrading is not feasible, implement network segmentation and restrict access to the SiPass server to trusted networks or IP addresses to reduce the attack surface.

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.90.3.8

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
None
Integrity
None
Availability
High

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

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

  1. Identify SiPass Integrated Server installation
    Locate the SiPass integrated server application in your environment. Check for processes named 'SiPass' or 'Sipass Integrated Server' running on the system, or look for the installation directory (typically under C:\Program Files\Siemens\SiPass or similar).
    Affected if SiPass integrated server is installed and running in your environment
  2. Determine installed SiPass version
    Right-click the SiPass executable or access Help > About in the SiPass management interface to view the exact version number. Compare this version against the affected range: any version below V2.90.3.8 is vulnerable.
    Affected if The installed version is lower than V2.90.3.8
  3. Verify configuration client login feature is enabled
    Check the SiPass server configuration settings to confirm whether the configuration client login functionality is enabled. This feature typically listens on TCP ports used by SiPass for client-server communication (commonly port 3000 or configurable).
    Affected if The configuration client login interface is exposed and accessible on the network
  4. Check network exposure of SiPass services
    Review firewall rules and network configurations to determine if the SiPass server ports are accessible from untrusted networks or the internet. Use netstat or firewall logs to identify external connectivity attempts.
    Affected if SiPass server ports are accessible from untrusted networks or directly from the internet

You are affected if SiPass Integrated Server is running with a version lower than V2.90.3.8 and the configuration client login feature is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 2.90.3.8 or later
Fixed in 2.90.3.8
Interim mitigation

Upgrade SiPass integrated to version V2.90.3.8 or later to patch the vulnerability. If immediate upgrading is not feasible, implement network segmentation and restrict access to the SiPass server to trusted networks or IP addresses to reduce the attack surface.

Recommended fix High confidence

SiPass Integrated V2.90.3.8

  1. 1. Identify the current version of SiPass Integrated by accessing the server management console or checking the application About/Help section
  2. 2. Navigate to the Siemens security advisory portal (cert-portal.siemens.com) or official Siemens support channels to obtain SiPass Integrated version 2.90.3.8 or later
  3. 3. Before upgrading, perform a complete backup of the SiPass Integrated database and configuration files
  4. 4. Stop the SiPass Integrated server application services
  5. 5. Install version 2.90.3.8 following the Siemens upgrade documentation procedures
  6. 6. Restart the SiPass Integrated server application services
  7. 7. Verify the server is running and accessible by attempting a configuration client login
  8. 8. Confirm the installed version is 2.90.3.8 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sipass Integrated Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
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,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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