dbcve.org
Wire ServerApplication · Wire

CVE-2022-31122

HIGH · 8.1 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to 2022-07-12 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 is an encrypted communication and collaboration platform. Versions prior to 2022-07-12/Chart 4.19.0 are subject to Token Recipient Confusion. If an attacker has certain details of SAML IdP metadata, and configures their own SAML on the same backend, the attacker can delete all SAML authenticated accounts of a targeted team, Authenticate as a user of the attacked team and create arbitrary accounts in the context of the team if it is not managed by SCIM. This issue is fixed in wire-server 2022-07-12 and is already deployed on all Wire managed services. On-premise instances of wire-server need to be updated to 2022-07-12/Chart 4.19.0, so that their backends are no longer affected. As a workaround, the risk of an attack can be reduced by disabling SAML configuration for teams (galley.config.settings.featureFlags.sso). Helm overrides are located in `values/wire-server/values.yaml` Note that the ability to configure SAML SSO as a team is disabled by default for on-premise installations.

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 Token Recipient Confusion vulnerability in Wire's SAML authentication allows an attacker with knowledge of certain SAML IdP metadata to configure their own SAML on the shared backend, enabling deletion of all SAML-authenticated accounts in a targeted team, authentication as any team user, and creation of arbitrary accounts in non-SCID-managed teams.

MitigationUpdate on-premise wire-server installations to version 2022-07-12 or Chart 4.19.0. As a workaround, disable SAML SSO for teams by setting galley.config.settings.featureFlags.sso to false in values/wire-server/values.yaml.

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:< 2022-07-12

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 the installed Wire Server version
    Check your wire-server deployment (via helm chart version, docker image tags, or package version) and compare it to the affected range: versions before 2022-07-12
    Affected if The installed version is any version prior to 2022-07-12
  2. Locate the SAML feature flag configuration
    Inspect your wire-server configuration files, typically in values/wire-server/values.yaml or the equivalent Helm values, and locate the featureFlags section
    Affected if The galley.config.settings.featureFlags.sso setting is present and set to true
  3. Verify SAML SSO is actively configured
    Check if any teams have SAML SSO enabled by querying Galley service API endpoints or reviewing team configuration that references SAML IdP metadata
    Affected if SAML IdP metadata has been configured for any team in the system
  4. Confirm shared backend SAML configuration
    Review whether SAML authentication is enabled at the backend level, allowing potential token recipient confusion between team-specific and shared backend tokens
    Affected if SAML authentication is enabled at the server level and multiple teams share the same backend infrastructure

A user is affected if their Wire Server version is before 2022-07-12 AND SAML SSO feature is enabled in the configuration, particularly on shared backend deployments.

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 2022-07-12 or later
Fixed in 2022-07-12
Interim mitigation

Update on-premise wire-server installations to version 2022-07-12 or Chart 4.19.0. As a workaround, disable SAML SSO for teams by setting galley.config.settings.featureFlags.sso to false in values/wire-server/values.yaml.

Recommended fix High confidence

wire-server 2022-07-12 / Helm Chart 4.19.0

  1. 1. Upgrade Wire Server to version 2022-07-12 or later (Helm Chart 4.19.0 or later)
  2. 2. For immediate mitigation before upgrading, disable SAML SSO by setting `galley.config.settings.featureFlags.sso: false` in your Helm values file (values/wire-server/values.yaml)
  3. 3. After upgrading, verify SAML authentication is functioning correctly for affected teams

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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