{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-65830 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-65830 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65830 is a critical vulnerability in n/a, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-65830 and fix it if it is affected.\n\nWhat it is: CVE-2025-65830 is a critical vulnerability in n/a, published on 10 Dec 2025. 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-2025-65830 in the wild and no public exploit code.\n\nAffected product: n/a. 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-65830/ (Markdown: https://insights.sbomify.com/CVE-2025-65830/index.md)","id":"CVE-2025-65830","markdown":"https://insights.sbomify.com/CVE-2025-65830/index.md","name":"CVE-2025-65830","record":{"aliases":["GHSA-524q-mw44-gx36"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Mobile application","requires_auth":"none","summary":"Attackers can intercept and modify TLS traffic due to missing certificate validation, potentially leading to account compromise via token theft or hash cracking.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"meatmeet","vendor":"meatmeet"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Due to a lack of certificate validation, all traffic from the mobile application can be intercepted. As a result, an adversary located \"upstream\" can decrypt the TLS traffic, inspect its contents, and modify the requests in transit. This may result in a total compromise of the user's account if the attacker intercepts a request with active authentication tokens or cracks the MD5 hash sent on login.","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":"Weak cryptography in n/a","id":"CVE-2025-65830","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2025-65831"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2025-65829"},"products":["n/a"],"published":"2025-12-10","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2025-65820","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-65826","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":9.1,"headline":"Weak cryptography in n/a","id":"CVE-2025-65827","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2025-65831","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":4.6,"headline":"Information disclosure in n/a","id":"CVE-2025-65832","kev_date_added":null,"published":"2025-12-10"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-11","vendors":["n/a"]},"summary":"Attackers can intercept and modify TLS traffic due to missing certificate validation, potentially leading to account compromise via token theft or hash cracking.","url":"https://insights.sbomify.com/CVE-2025-65830/"}