CORS `Access-Control-Allow-Origin` settings are too lenient
Description
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).
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
2- Range: <2.106.0
- wireapp/wire-serverv5Range: < 2.106.0
Patches
Vulnerability mechanics
References
1- github.com/wireapp/wire-server/security/advisories/GHSA-v7xx-cx8m-g66pmitrex_refsource_CONFIRM
News mentions
0No linked articles in our index yet.