{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23610 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-23610 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23610 is a critical authentication bypass vulnerability in wireapp wire-server, published on 16 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23610 and fix it if it is affected.\n\nWhat it is: CVE-2022-23610 is a critical authentication bypass vulnerability in wireapp wire-server, published on 16 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-23610 in the wild and no public exploit code.\n\nAffected product: wireapp wire-server. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-23610/ (Markdown: https://insights.sbomify.com/CVE-2022-23610/index.md)","id":"CVE-2022-23610","markdown":"https://insights.sbomify.com/CVE-2022-23610/index.md","name":"CVE-2022-23610","record":{"aliases":["GHSA-9jg9-9g37-4424"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Wire backend server","requires_auth":"none","summary":"Attackers can bypass SAML SSO authentication to impersonate users or create accounts in Wire teams with SAML enabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wire-server","vendor":"wire"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Improper Verification of Cryptographic Signature in wire-server","id":"CVE-2022-23610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"OS command injection in iTunesRPC-Remastered","id":"CVE-2022-23611"},"packages":[],"prev":{"headline":"Path traveresal in iTunesRPC-Remastered","id":"CVE-2022-23609"},"products":["wire-server"],"published":"2022-03-16","related":[{"cvss_score":7.4,"headline":"Account takeover when having only access to a user's short lived token in wire-server","id":"CVE-2021-41100","kev_date_added":null,"published":"2021-10-04"},{"cvss_score":5.3,"headline":"DoS vulnerabiliity in wire-server json parser","id":"CVE-2021-41119","kev_date_added":null,"published":"2022-04-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["wireapp"]},"summary":"Attackers can bypass SAML SSO authentication to impersonate users or create accounts in Wire teams with SAML enabled.","url":"https://insights.sbomify.com/CVE-2022-23610/"}