First published: Thu Sep 30 2021(Updated: )
wire-server is an open-source back end for Wire, a secure collaboration platform. Before version 2.106.0, the CORS ` Access-Control-Allow-Origin ` header set by `nginz` is set for all subdomains of `.wire.com` (including `wire.com`). This means that if somebody were to find an XSS vector in any of the subdomains, they could use it to talk to the Wire API using the user's Cookie. A patch does not exist, but a workaround does. To make sure that a compromise of one subdomain does not yield access to the cookie of another, one may limit the `Access-Control-Allow-Origin` header to apps that actually require the cookie (account-pages, team-settings and the webapp).
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Wire | <2.106.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this issue is CVE-2021-41101.
The severity of CVE-2021-41101 is medium with a CVSS score of 5.7.
The affected software is Wire Server before version 2.106.0.
The CWE ID for this vulnerability is CWE-79.
Yes, you can find more information about the vulnerability in the Wire Server security advisory on GitHub: https://github.com/wireapp/wire-server/security/advisories/GHSA-v7xx-cx8m-g66p