{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-20630 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-20630 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-20630 is a medium-severity denial of service vulnerability in Mattermost, published on 16 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-20630 and fix it if it is affected.\n\nWhat it is: CVE-2025-20630 is a medium-severity denial of service vulnerability in Mattermost, published on 16 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-20630 in the wild and no public exploit code.\n\nAffected product: Mattermost. 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-2025-20630/ (Markdown: https://insights.sbomify.com/CVE-2025-20630/index.md)","id":"CVE-2025-20630","markdown":"https://insights.sbomify.com/CVE-2025-20630/index.md","name":"CVE-2025-20630","record":{"aliases":["GHSA-93w4-x8jh-j7m2"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Mattermost mobile app","requires_auth":"low_privilege","summary":"An attacker can crash the Mattermost mobile application by sending a post with attachment fields that cannot be cast to a String.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Mattermost","cpe":[{"product":"mattermost_mobile","vendor":"mattermost"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1287","name":"Improper Validation of Specified Type of Input"}],"description":"Mattermost Mobile versions \u003c=2.22.0 fail to properly handle posts with attachments containing fields that cannot be cast to a String, which allows an attacker to cause the mobile to crash via creating and sending such a post to a channel.","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":"Mobile crash via object that can't be cast to String in Attachment Field","id":"CVE-2025-20630","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986","id":"CVE-2025-20631"},"packages":[],"prev":{"headline":"Privilege escalation in Intel(R) Ethernet Network Adapter E810 Series","id":"CVE-2025-20629"},"products":["Mattermost"],"published":"2025-01-16","related":[{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2019-20848","kev_date_added":null,"published":"2020-06-19"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2019-20852","kev_date_added":null,"published":"2020-06-19"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-14449","kev_date_added":null,"published":"2020-06-19"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-14451","kev_date_added":null,"published":"2020-06-19"},{"cvss_score":6.5,"headline":"Denial of Service Via Malicious GIF","id":"CVE-2025-1558","kev_date_added":null,"published":"2025-03-24"},{"cvss_score":6.5,"headline":"Mobile crash via improper validation of proto style in attachments","id":"CVE-2025-20072","kev_date_added":null,"published":"2025-01-16"}],"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-01-16","vendors":["Mattermost"]},"summary":"An attacker can crash the Mattermost mobile application by sending a post with attachment fields that cannot be cast to a String.","url":"https://insights.sbomify.com/CVE-2025-20630/"}