dbcve.org
Wire ServerApplication · Wire

CVE-2022-23610

HIGH · 8.1 CVSS v3.1 Published 2022-03-16
Fix available
A fix is available. Upgrade to 2.123.0 or later.
See remediation →
90/100
Remediation priority · Urgent
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
wire-server provides back end services for Wire, an open source messenger. In versions of wire-server prior to the 2022-01-27 release, it was possible to craft DSA Signatures to bypass SAML SSO and impersonate any Wire user with SAML credentials. In teams with SAML, but without SCIM, it was possible to create new accounts with fake SAML credentials. Under certain conditions that can be established by an attacker, an upstream library for parsing, rendering, signing, and validating SAML XML data was accepting public keys as trusted that were provided by the attacker in the signature. As a consequence, the attacker could login as any user in any Wire team with SAML SSO enabled. If SCIM was not enabled, the attacker could also create new users with new SAML NameIDs. In order to exploit this vulnerability, the attacker needs to know the SSO login code (distributed to all team members with SAML credentials and visible in the Team Management app), the SAML EntityID identifying the IdP (a URL not considered sensitive, but usually hard to guess, also visible in Team Management), and the SAML NameID of the user (usually an email address or a nick). The issue has been fixed in wire-server `2022-01-27` and is already deployed on all Wire managed services. On premise instances of wire-server need to be updated to `2022-01-27`, so that their backends are no longer affected. There are currently no known workarounds. More detailed information about how to reproduce the vulnerability and mitigation strategies is available in the GitHub Security Advisory.

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

In wire-server versions prior to 2022-01-27, an upstream SAML library accepted attacker-provided public keys as trusted within DSA signatures, allowing authentication bypass. An attacker with knowledge of the SSO login code, SAML EntityID, and target user's NameID could forge signatures and impersonate any SAML-enabled user, or create new unauthorized accounts if SCIM was not enabled.

MitigationUpdate wire-server to version 2022-01-27 or later to patch the vulnerable SAML library. No workarounds exist; on-premise deployments must apply the update.

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
Wire ServerApplication
Affected:< 2.123.0

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
High

CVSS:3.1/AV:N/AC:H/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 checks

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

  1. Identify if wire-server is installed
    Check for the presence of wire-server components in your environment, such as via package manager, container images, or deployment manifests
    Affected if wire-server is present in the environment
  2. Determine the installed wire-server version
    Retrieve the version of wire-server using your deployment tooling (e.g., helm chart version, container image tag, or package version)
    Affected if the version is lower than 2.123.0
  3. Check if SAML SSO is enabled
    Inspect the wire-server configuration for SAML SP (Service Provider) settings, such as SAML EntityID, SSO endpoints, or identity provider configuration
    Affected if SAML authentication is enabled in the wire-server deployment

You are affected if wire-server version is below 2.123.0 AND SAML/SSO authentication is enabled in your deployment

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.123.0 or later
Fixed in 2.123.0
Interim mitigation

Update wire-server to version 2022-01-27 or later to patch the vulnerable SAML library. No workarounds exist; on-premise deployments must apply the update.

Recommended fix High confidence

wire-server 2022-01-27 (version 2.123.0 or later)

  1. Upgrade wire-server to the 2022-01-27 release (also known as version 2.123.0 or later)
  2. After upgrading, verify that SAML SSO authentication is functioning correctly
  3. Confirm that the SAML IdP configuration remains valid after the update
  4. Test user authentication with SAML credentials to ensure the signature verification fix is working

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

Fix this in Wire Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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