{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-31009 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-31009 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-31009 is a medium-severity denial of service vulnerability in wireapp wire-ios, published on 23 Jun 2022. 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-2022-31009 and fix it if it is affected.\n\nWhat it is: CVE-2022-31009 is a medium-severity denial of service vulnerability in wireapp wire-ios, published on 23 Jun 2022. 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-2022-31009 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-2022-31009/ (Markdown: https://insights.sbomify.com/CVE-2022-31009/index.md)","id":"CVE-2022-31009","markdown":"https://insights.sbomify.com/CVE-2022-31009/index.md","name":"CVE-2022-31009","record":{"aliases":["GHSA-83m6-p7x5-925j"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Wire iOS client","requires_auth":"low_privilege","summary":"An attacker can cause the Wire iOS client to crash repeatedly by sending invalid accent colors, requiring users to upgrade the application.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wire","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:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"}],"description":"wire-ios is an iOS client for the Wire secure messaging application. Invalid accent colors of Wire communication partners may render the iOS Wire Client partially unusable by causing it to crash multiple times on launch. These invalid accent colors can be used by and sent between Wire users. The root cause was an unnecessary assert statement when converting an integer value into the corresponding enum value, causing an exception instead of a fallback to a default value. This issue is fixed in [wire-ios](https://github.com/wireapp/wire-ios/commit/caa0e27dbe51f9edfda8c7a9f017d93b8cfddefb) and in Wire for iOS 3.100. There is no workaround available, but users may use other Wire clients (such as the [web app](https://app.wire.com)) to continue using Wire, or upgrade their client.","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":"DoS vulnerability: Invalid Accent Colors","id":"CVE-2022-31009","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"TiDB authentication bypass vulnerability","id":"CVE-2022-31011"},"packages":[],"prev":{"headline":"Predictable credential obfuscation seed value used in rabbitmq-server","id":"CVE-2022-31008"},"products":["wire-ios"],"published":"2022-06-23","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.8,"headline":"Verified groups not reliable","id":"CVE-2021-32665","kev_date_added":null,"published":"2021-06-03"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["wireapp"]},"summary":"An attacker can cause the Wire iOS client to crash repeatedly by sending invalid accent colors, requiring users to upgrade the application.","url":"https://insights.sbomify.com/CVE-2022-31009/"}