{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48925 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-48925 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48925 is a medium-severity vulnerability in TeleMessage service, published on 28 May 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-48925 and fix it if it is affected.\n\nWhat it is: CVE-2025-48925 is a medium-severity vulnerability in TeleMessage service, published on 28 May 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-48925 in the wild and no public exploit code.\n\nAffected product: TeleMessage service. 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-48925/ (Markdown: https://insights.sbomify.com/CVE-2025-48925/index.md)","id":"CVE-2025-48925","markdown":"https://insights.sbomify.com/CVE-2025-48925/index.md","name":"CVE-2025-48925","record":{"aliases":["GHSA-g7m2-hjxw-27h7"],"analysis":{"component_type":"cloud_service","fix_type":"no_fix_stated","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TeleMessage secure messaging","requires_auth":"low_privilege","summary":"The TeleMessage service uses weak MD5 hashing for authentication, allowing attackers to potentially bypass security and take over accounts.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telemessage","vendor":"smarsh"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-836","name":"Use of Password Hash Instead of Password for Authentication"}],"description":"The TeleMessage service through 2025-05-05 relies on the client side (e.g., the TM SGNL app) to do MD5 hashing, and then accepts the hash as the authentication credential.","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 service","id":"CVE-2025-48925","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in service","id":"CVE-2025-48926"},"packages":[],"prev":{"headline":"Apache Commons Lang, Apache Commons Lang: ClassUtils.getClass(...) can throw a StackOverflowError on very long inputs","id":"CVE-2025-48924"},"products":["service"],"published":"2025-05-28","related":[{"cvss_score":5.3,"headline":"TeleMessage TM SGNL Initialization of a Resource with an Insecure Default","id":"CVE-2025-48927","kev_date_added":"2025-07-01","published":"2025-05-28"},{"cvss_score":4,"headline":"TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere","id":"CVE-2025-48928","kev_date_added":"2025-07-01","published":"2025-05-28"},{"cvss_score":4.8,"headline":"Hardcoded credentials in archiving backend","id":"CVE-2025-47730","kev_date_added":null,"published":"2025-05-08"},{"cvss_score":4.3,"headline":"Information disclosure in service","id":"CVE-2025-48926","kev_date_added":null,"published":"2025-05-28"},{"cvss_score":4,"headline":"Auth bypass in service","id":"CVE-2025-48929","kev_date_added":null,"published":"2025-05-28"},{"cvss_score":3.2,"headline":"Weak cryptography in service","id":"CVE-2025-48931","kev_date_added":null,"published":"2025-05-28"}],"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-07-01","vendors":["TeleMessage"]},"summary":"The TeleMessage service uses weak MD5 hashing for authentication, allowing attackers to potentially bypass security and take over accounts.","url":"https://insights.sbomify.com/CVE-2025-48925/"}