{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41904 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41904 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41904 is a medium-severity vulnerability in vector-im element-ios, published on 11 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-41904 and fix it if it is affected.\n\nWhat it is: CVE-2022-41904 is a medium-severity vulnerability in vector-im element-ios, published on 11 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-41904 in the wild and no public exploit code.\n\nAffected product: vector-im element-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-2022-41904/ (Markdown: https://insights.sbomify.com/CVE-2022-41904/index.md)","id":"CVE-2022-41904","markdown":"https://insights.sbomify.com/CVE-2022-41904/index.md","name":"CVE-2022-41904","record":{"aliases":["GHSA-fm8m-99j7-323g"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Element iOS client","requires_auth":"low_privilege","summary":"A malicious homeserver can inject unverified messages into Element iOS chats without triggering security warnings, bypassing user trust indicators.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"element","vendor":"element"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-357","name":"Insufficient UI Warning of Dangerous Operations"}],"description":"Element iOS is an iOS Matrix client provided by Element. It is based on MatrixSDK. Prior to version 1.9.7, events encrypted using Megolm for which trust could not be established did not get decorated accordingly (with warning shields). Therefore a malicious homeserver could inject messages into the room without the user being alerted that the messages were not sent by a verified group member, even if the user has previously verified all group members. This issue has been patched in Element iOS 1.9.7. There are currently no known workarounds.","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":"Element iOS is vulnerable due to missing decoration for events decrypted with untrusted Megolm sessions","id":"CVE-2022-41904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"wsgidav is vulnerable to Cross-Site Scripting (XSS) when directory browsing is enabled","id":"CVE-2022-41905"},"packages":[],"prev":{"headline":"Integer overflow in `git archive`, `git log --format` leading to RCE in git","id":"CVE-2022-41903"},"products":["element-ios"],"published":"2022-11-11","related":[{"cvss_score":8.4,"headline":"Element Android Intent Redirection","id":"CVE-2024-26131","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":5.1,"headline":"Element Android PIN autologout bypass","id":"CVE-2025-27606","kev_date_added":null,"published":"2025-03-14"},{"cvss_score":4,"headline":"Element Android can be asked to share internal files.","id":"CVE-2024-26132","kev_date_added":null,"published":"2024-02-20"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["vector-im"]},"summary":"A malicious homeserver can inject unverified messages into Element iOS chats without triggering security warnings, bypassing user trust indicators.","url":"https://insights.sbomify.com/CVE-2022-41904/"}