{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32665 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-32665 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32665 is a high-severity vulnerability in wireapp wire-ios, published on 3 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32665 and fix it if it is affected.\n\nWhat it is: CVE-2021-32665 is a high-severity vulnerability in wireapp wire-ios, published on 3 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32665 in the wild and no public exploit code.\n\nAffected product: wireapp wire-ios. 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-32665/ (Markdown: https://insights.sbomify.com/CVE-2021-32665/index.md)","id":"CVE-2021-32665","markdown":"https://insights.sbomify.com/CVE-2021-32665/index.md","name":"CVE-2021-32665","record":{"aliases":["GHSA-mc3m-xwph-4h9h"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Wire iOS messaging app","requires_auth":"low_privilege","summary":"Attackers can bypass device verification in Wire iOS conversations, allowing unverified devices to appear trusted under specific conditions.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wire","vendor":"wire"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"wire-ios is the iOS version of Wire, an open-source secure messaging app. wire-ios versions 3.8.0 and earlier have a bug in which a conversation could be incorrectly set to \"unverified. This occurs when: - Self user is added to a new conversation - Self user is added to an existing conversation - All the participants in the conversation were previously marked as verified. The vulnerability is patched in wire-ios version 3.8.1. As a workaround, one can unverify \u0026 verify a device in the conversation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Verified groups not reliable","id":"CVE-2021-32665","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Asset DoS vulnerability","id":"CVE-2021-32666"},"packages":[],"prev":{"headline":"Reflected XSS in Combodo/iTop","id":"CVE-2021-32664"},"products":["wire-ios"],"published":"2021-06-03","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2020-27853","kev_date_added":null,"published":"2020-10-27"},{"cvss_score":8,"headline":"Insecure use of shell.openExternal in Wire","id":"CVE-2020-15258","kev_date_added":null,"published":"2020-10-16"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2018-8909","kev_date_added":null,"published":"2018-03-22"},{"cvss_score":7.4,"headline":"Account takeover when having only access to a user's short lived token","id":"CVE-2021-41093","kev_date_added":null,"published":"2021-10-04"},{"cvss_score":6.5,"headline":"wire-server vulnerable to unauthorized removal of Bots from Conversations","id":"CVE-2023-22737","kev_date_added":null,"published":"2023-01-27"},{"cvss_score":6.5,"headline":"DoS vulnerability: Malformed Resource Identifiers","id":"CVE-2022-23625","kev_date_added":null,"published":"2022-03-11"}],"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-03","vendors":["wireapp"]},"summary":"Attackers can bypass device verification in Wire iOS conversations, allowing unverified devices to appear trusted under specific conditions.","url":"https://insights.sbomify.com/CVE-2021-32665/"}