{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41101 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41101 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41101 is a medium-severity vulnerability in wireapp wire-server, published on 30 Sep 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-41101 and fix it if it is affected.\n\nWhat it is: CVE-2021-41101 is a medium-severity vulnerability in wireapp wire-server, published on 30 Sep 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-41101 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-2021-41101/ (Markdown: https://insights.sbomify.com/CVE-2021-41101/index.md)","id":"CVE-2021-41101","markdown":"https://insights.sbomify.com/CVE-2021-41101/index.md","name":"CVE-2021-41101","record":{"aliases":["GHSA-v7xx-cx8m-g66p"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Wire backend server","requires_auth":"low_privilege","summary":"Lenient CORS settings allow attackers to exploit XSS on subdomains to access user cookies and interact with the Wire API.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wire_server","vendor":"wire"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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).","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":"CORS `Access-Control-Allow-Origin` settings are too lenient","id":"CVE-2021-41101","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Insufficiently restricted permissions on plugin directories","id":"CVE-2021-41103"},"packages":[],"prev":{"headline":"Account takeover when having only access to a user's short lived token in wire-server","id":"CVE-2021-41100"},"products":["wire-server"],"published":"2021-09-30","related":[{"cvss_score":9.8,"headline":"Auth bypass in wire-server","id":"CVE-2022-31122","kev_date_added":null,"published":"2022-10-18"},{"cvss_score":6.5,"headline":"Bulk list client endpoint exposes too much metadata about a client","id":"CVE-2021-21396","kev_date_added":null,"published":"2021-03-26"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["wireapp"]},"summary":"Lenient CORS settings allow attackers to exploit XSS on subdomains to access user cookies and interact with the Wire API.","url":"https://insights.sbomify.com/CVE-2021-41101/"}