{"api_version":"1","generated_at":"2026-07-24T02:25:26+00:00","cve":"CVE-2021-41101","urls":{"html":"https://cve.report/CVE-2021-41101","api":"https://cve.report/api/cve/CVE-2021-41101.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2021-41101","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2021-41101"},"summary":{"title":"CVE-2021-41101","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).","state":"PUBLIC","assigner":"security-advisories@github.com","published_at":"2021-09-30 20:15:00","updated_at":"2021-10-07 22:45:00"},"problem_types":["CWE-79"],"metrics":[],"references":[{"url":"https://github.com/wireapp/wire-server/security/advisories/GHSA-v7xx-cx8m-g66p","name":"https://github.com/wireapp/wire-server/security/advisories/GHSA-v7xx-cx8m-g66p","refsource":"CONFIRM","tags":[],"title":"CORS `Access-Control-Allow-Origin` settings are too lenient · Advisory · wireapp/wire-server · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-41101","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-41101","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2021","cve_id":"41101","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"wire","cpe5":"wire_server","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2021-41101","STATE":"PUBLIC","TITLE":"CORS `Access-Control-Allow-Origin` settings are too lenient"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"wire-server","version":{"version_data":[{"version_value":"< 2.106.0"}]}}]},"vendor_name":"wireapp"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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)."}]},"impact":{"cvss":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":5.7,"baseSeverity":"MEDIUM","confidentialityImpact":"HIGH","integrityImpact":"NONE","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"REQUIRED","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')"}]}]},"references":{"reference_data":[{"name":"https://github.com/wireapp/wire-server/security/advisories/GHSA-v7xx-cx8m-g66p","refsource":"CONFIRM","url":"https://github.com/wireapp/wire-server/security/advisories/GHSA-v7xx-cx8m-g66p"}]},"source":{"advisory":"GHSA-v7xx-cx8m-g66p","discovery":"UNKNOWN"}},"nvd":{"publishedDate":"2021-09-30 20:15:00","lastModifiedDate":"2021-10-07 22:45:00","problem_types":["CWE-79"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":5.7,"baseSeverity":"MEDIUM"},"exploitabilityScore":2.1,"impactScore":3.6},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:M/Au:S/C:P/I:N/A:N","accessVector":"NETWORK","accessComplexity":"MEDIUM","authentication":"SINGLE","confidentialityImpact":"PARTIAL","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":3.5},"severity":"LOW","exploitabilityScore":6.8,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":true}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:wire:wire_server:*:*:*:*:*:*:*:*","versionEndExcluding":"2.106.0","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2021","CveId":"41101","Ordinal":"216895","Title":"CVE-2021-41101","CVE":"CVE-2021-41101","Year":"2021"},"notes":[{"CveYear":"2021","CveId":"41101","Ordinal":"1","NoteData":"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).","Type":"Description","Title":null},{"CveYear":"2021","CveId":"41101","Ordinal":"2","NoteData":"2021-09-30","Type":"Other","Title":"Published"},{"CveYear":"2021","CveId":"41101","Ordinal":"3","NoteData":"2021-09-30","Type":"Other","Title":"Modified"}]}}}