{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53605 exists.","fix":"No fix has been published for CVE-2024-53605 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-53605 is a high-severity missing authorization vulnerability in n/a, published on 2 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-53605 and fix it if it is affected.\n\nWhat it is: CVE-2024-53605 is a high-severity missing authorization vulnerability in n/a, published on 2 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53605 exists.\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-2024-53605/ (Markdown: https://insights.sbomify.com/CVE-2024-53605/index.md)","id":"CVE-2024-53605","markdown":"https://insights.sbomify.com/CVE-2024-53605/index.md","name":"CVE-2024-53605","record":{"aliases":["GHSA-cc44-h482-gj5h"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Handcent NextSMS","requires_auth":"none","summary":"Attackers can access sensitive data via the MessageProvider due to incorrect access control in Handcent NextSMS.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Incorrect access control in the component content://com.handcent.messaging.provider.MessageProvider/ of Handcent NextSMS v10.9.9.7 allows attackers to access sensitive data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2024-53605","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2024-53614"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2024-53604"},"products":["n/a"],"published":"2024-12-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-04","vendors":["n/a"]},"summary":"Attackers can access sensitive data via the MessageProvider due to incorrect access control in Handcent NextSMS.","url":"https://insights.sbomify.com/CVE-2024-53605/"}