{"containers": {"cna": {"affected": [{"product": "wire-server", "vendor": "wireapp", "versions": [{"status": "affected", "version": "< 2022-01-27"}, {"status": "affected", "version": "< 2.123.0"}]}], "descriptions": [{"lang": "en", "value": "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."}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 9.1, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "version": "3.1"}}], "problemTypes": [{"descriptions": [{"cweId": "CWE-347", "description": "CWE-347: Improper Verification of Cryptographic Signature", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"dateUpdated": "2022-03-16T17:40:10", "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M"}, "references": [{"tags": ["x_refsource_CONFIRM"], "url": "https://github.com/wireapp/wire-server/security/advisories/GHSA-9jg9-9g37-4424"}, {"tags": ["x_refsource_MISC"], "url": "https://github.com/wireapp/wire-server/releases/tag/v2022-01-27"}], "source": {"advisory": "GHSA-9jg9-9g37-4424", "discovery": "UNKNOWN"}, "title": "Improper Verification of Cryptographic Signature in wire-server", "x_legacyV4Record": {"CVE_data_meta": {"ASSIGNER": "[email protected]", "ID": "CVE-2022-23610", "STATE": "PUBLIC", "TITLE": "Improper Verification of Cryptographic Signature in wire-server"}, "affects": {"vendor": {"vendor_data": [{"product": {"product_data": [{"product_name": "wire-server", "version": {"version_data": [{"version_value": "< 2022-01-27"}, {"version_value": "< 2.123.0"}]}}]}, "vendor_name": "wireapp"}]}}, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": {"description_data": [{"lang": "eng", "value": "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."}]}, "impact": {"cvss": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 9.1, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "version": "3.1"}}, "problemtype": {"problemtype_data": [{"description": [{"lang": "eng", "value": "CWE-347: Improper Verification of Cryptographic Signature"}]}]}, "references": {"reference_data": [{"name": "https://github.com/wireapp/wire-server/security/advisories/GHSA-9jg9-9g37-4424", "refsource": "CONFIRM", "url": "https://github.com/wireapp/wire-server/security/advisories/GHSA-9jg9-9g37-4424"}, {"name": "https://github.com/wireapp/wire-server/releases/tag/v2022-01-27", "refsource": "MISC", "url": "https://github.com/wireapp/wire-server/releases/tag/v2022-01-27"}]}, "source": {"advisory": "GHSA-9jg9-9g37-4424", "discovery": "UNKNOWN"}}}, "adp": [{"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-03T03:43:46.981Z"}, "title": "CVE Program Container", "references": [{"tags": ["x_refsource_CONFIRM", "x_transferred"], "url": "https://github.com/wireapp/wire-server/security/advisories/GHSA-9jg9-9g37-4424"}, {"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://github.com/wireapp/wire-server/releases/tag/v2022-01-27"}]}]}, "cveMetadata": {"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "assignerShortName": "GitHub_M", "cveId": "CVE-2022-23610", "datePublished": "2022-03-16T17:40:10", "dateReserved": "2022-01-19T00:00:00", "dateUpdated": "2024-08-03T03:43:46.981Z", "state": "PUBLISHED"}, "dataType": "CVE_RECORD", "dataVersion": "5.1"}

{}

{"configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:wire:wire-server:*:*:*:*:*:*:*:*", "matchCriteriaId": "5BFE84F1-6855-4EE7-8838-39A8B374C46C", "versionEndExcluding": "2.123.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "wire-server proporciona servicios de back-end para Wire, un mensajero de c\u00f3digo abierto. En versiones de wire-server anteriores a 27-01-2022, era posible dise\u00f1ar firmas DSA para omitir el SSO de SAML y suplantar a cualquier usuario de Wire con credenciales SAML. En equipos con SAML, pero sin SCIM, era posible crear nuevas cuentas con credenciales SAML falsas. Bajo determinadas condiciones que pueden ser establecidas por un atacante, una biblioteca upstream para analizar, renderizar, firmar y comprobar datos XML de SAML aceptaba como confiables claves p\u00fablicas que eran proporcionadas por el atacante en la firma. Como consecuencia, el atacante pod\u00eda iniciar sesi\u00f3n como cualquier usuario en cualquier equipo de Wire con SAML SSO habilitado. Si SCIM no estaba habilitado, el atacante tambi\u00e9n pod\u00eda crear nuevos usuarios con nuevos NameID de SAML. Para explotar esta vulnerabilidad, el atacante necesita conocer el c\u00f3digo de inicio de sesi\u00f3n de SSO (distribuido a todos los miembros del equipo con credenciales SAML y visible en la aplicaci\u00f3n de administraci\u00f3n de equipos), el EntityID de SAML que identifica al IdP (una URL no considerada confidencial, pero normalmente dif\u00edcil de adivinar, tambi\u00e9n visible en la administraci\u00f3n de equipos) y el NameID de SAML del usuario (normalmente una direcci\u00f3n de correo electr\u00f3nico o un nick). El problema ha sido solucionado en wire-server \"27-01-2022\" y ya est\u00e1 desplegado en todos los servicios gestionados de Wire. Las instancias locales de wire-server deben ser actualizadas a \"27-01-2022\", para que sus backends no est\u00e9n afectados. Actualmente no se presentan medidas de mitigaci\u00f3n conocidas. Se presenta informaci\u00f3n m\u00e1s detallada sobre c\u00f3mo reproducir la vulnerabilidad y las estrategias de mitigaci\u00f3n en el aviso de seguridad de GitHub"}], "id": "CVE-2022-23610", "lastModified": "2024-11-21T06:48:55.640", "metrics": {"cvssMetricV2": [{"acInsufInfo": false, "baseSeverity": "MEDIUM", "cvssData": {"accessComplexity": "HIGH", "accessVector": "NETWORK", "authentication": "NONE", "availabilityImpact": "PARTIAL", "baseScore": 5.1, "confidentialityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "vectorString": "AV:N/AC:H/Au:N/C:P/I:P/A:P", "version": "2.0"}, "exploitabilityScore": 4.9, "impactScore": 6.4, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "source": "[email protected]", "type": "Primary", "userInteractionRequired": false}], "cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 9.1, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 5.2, "source": "[email protected]", "type": "Secondary"}, {"cvssData": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 8.1, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 2.2, "impactScore": 5.9, "source": "[email protected]", "type": "Primary"}]}, "published": "2022-03-16T18:15:11.617", "references": [{"source": "[email protected]", "tags": ["Release Notes", "Third Party Advisory"], "url": "https://github.com/wireapp/wire-server/releases/tag/v2022-01-27"}, {"source": "[email protected]", "tags": ["Mitigation", "Third Party Advisory"], "url": "https://github.com/wireapp/wire-server/security/advisories/GHSA-9jg9-9g37-4424"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Release Notes", "Third Party Advisory"], "url": "https://github.com/wireapp/wire-server/releases/tag/v2022-01-27"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Mitigation", "Third Party Advisory"], "url": "https://github.com/wireapp/wire-server/security/advisories/GHSA-9jg9-9g37-4424"}], "sourceIdentifier": "[email protected]", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-347"}], "source": "[email protected]", "type": "Secondary"}]}

{}