{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41100 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41100 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41100 is a high-severity authentication bypass vulnerability in wireapp wire-server, published on 4 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41100 and fix it if it is affected.\n\nWhat it is: CVE-2021-41100 is a high-severity authentication bypass vulnerability in wireapp wire-server, published on 4 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-41100 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-41100/ (Markdown: https://insights.sbomify.com/CVE-2021-41100/index.md)","id":"CVE-2021-41100","markdown":"https://insights.sbomify.com/CVE-2021-41100/index.md","name":"CVE-2021-41100","record":{"aliases":["GHSA-9rm2-w6pq-333m"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Wire secure messaging server","requires_auth":"none","summary":"Attackers can take over user accounts by changing email addresses using only short-lived session tokens, bypassing intended authentication restrictions.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wire-server","vendor":"wire"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"Wire-server is the backing server for the open source wire secure messaging application. In affected versions it is possible to trigger email address change of a user with only the short-lived session token in the `Authorization` header. As the short-lived token is only meant as means of authentication by the client for less critical requests to the backend, the ability to change the email address with a short-lived token constitutes a privilege escalation attack. Since the attacker can change the password after setting the email address to one that they control, changing the email address can result in an account takeover by the attacker. Short-lived tokens can be requested from the backend by Wire clients using the long lived tokens, after which the long lived tokens can be stored securely, for example on the devices key chain. The short lived tokens can then be used to authenticate the client towards the backend for frequently performed actions such as sending and receiving messages. While short-lived tokens should not be available to an attacker per-se, they are used more often and in the shape of an HTTP header, increasing the risk of exposure to an attacker relative to the long-lived tokens, which are stored and transmitted in cookies. If you are running an on-prem instance and provision all users with SCIM, you are not affected by this issue (changing email is blocked for SCIM users). SAML single-sign-on is unaffected by this issue, and behaves identically before and after this update. The reason is that the email address used as SAML NameID is stored in a different location in the databse from the one used to contact the user outside wire. Version 2021-08-16 and later provide a new end-point that requires both the long-lived client cookie and `Authorization` header. The old end-point has been removed. If you are running an on-prem instance with at least some of the users invited or provisioned via SAML SSO and you cannot update then you can block `/self/email` on nginz (or in any other proxies or firewalls you may have set up). You don't need to discriminate by verb: `/self/email` only accepts `PUT` and `DELETE`, and `DELETE` is almost never used.","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":"Account takeover when having only access to a user's short lived token in wire-server","id":"CVE-2021-41100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"CORS `Access-Control-Allow-Origin` settings are too lenient","id":"CVE-2021-41101"},"packages":[],"prev":{"headline":"Integer overflow issue with strings in Redis","id":"CVE-2021-41099"},"products":["wire-server"],"published":"2021-10-04","related":[{"cvss_score":9.1,"headline":"Improper Verification of Cryptographic Signature in wire-server","id":"CVE-2022-23610","kev_date_added":null,"published":"2022-03-16"},{"cvss_score":5.3,"headline":"DoS vulnerabiliity in wire-server json parser","id":"CVE-2021-41119","kev_date_added":null,"published":"2022-04-13"}],"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":"Attackers can take over user accounts by changing email addresses using only short-lived session tokens, bypassing intended authentication restrictions.","url":"https://insights.sbomify.com/CVE-2021-41100/"}