{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48929 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-48929 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48929 is a medium-severity authentication bypass vulnerability in TeleMessage service, published on 28 May 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-48929 and fix it if it is affected.\n\nWhat it is: CVE-2025-48929 is a medium-severity authentication bypass vulnerability in TeleMessage service, published on 28 May 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-48929 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-48929/ (Markdown: https://insights.sbomify.com/CVE-2025-48929/index.md)","id":"CVE-2025-48929","markdown":"https://insights.sbomify.com/CVE-2025-48929/index.md","name":"CVE-2025-48929","record":{"aliases":["GHSA-5wx3-hjmf-qcgx"],"analysis":{"component_type":"cloud_service","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"TeleMessage service","requires_auth":"none","summary":"Attackers can reuse long-lived credentials to hijack accounts if the credentials are discovered, affecting TeleMessage service users.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telemessage","vendor":"smarsh"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"},{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"The TeleMessage service through 2025-05-05 implements authentication through a long-lived credential (e.g., not a token with a short expiration time) that can be reused at a later date if discovered by an adversary.","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":"Auth bypass in service","id":"CVE-2025-48929","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in service","id":"CVE-2025-48930"},"packages":[],"prev":{"headline":"TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere","id":"CVE-2025-48928"},"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":"Weak cryptography in service","id":"CVE-2025-48925","kev_date_added":null,"published":"2025-05-28"},{"cvss_score":4.3,"headline":"Information disclosure in service","id":"CVE-2025-48926","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":"Attackers can reuse long-lived credentials to hijack accounts if the credentials are discovered, affecting TeleMessage service users.","url":"https://insights.sbomify.com/CVE-2025-48929/"}