{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-36558 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-36558 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-36558 is a high-severity vulnerability in n/a, published on 6 Feb 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-2024-36558 and fix it if it is affected.\n\nWhat it is: CVE-2024-36558 is a high-severity vulnerability in n/a, published on 6 Feb 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-2024-36558 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-2024-36558/ (Markdown: https://insights.sbomify.com/CVE-2024-36558/index.md)","id":"CVE-2024-36558","markdown":"https://insights.sbomify.com/CVE-2024-36558/index.md","name":"CVE-2024-36558","record":{"aliases":["GHSA-6r5f-5cgm-ff5g"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"KidsWatch smartwatch","requires_auth":"none","summary":"Attackers can intercept sensitive data transmitted between the KidsWatch smartwatch and its server due to lack of encryption.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"Forever KidsWatch Call Me KW-50 R36_YDR_A3PW_GM7S_V1.0_2019_07_15_16.19.24_cob_h suffers from Cleartext Transmission of Sensitive Information due to lack of encryption in device-server communication.","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":"Information disclosure in n/a","id":"CVE-2024-36558","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2024-36568"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2024-36557"},"products":["n/a"],"published":"2025-02-06","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-19","vendors":["n/a"]},"summary":"Attackers can intercept sensitive data transmitted between the KidsWatch smartwatch and its server due to lack of encryption.","url":"https://insights.sbomify.com/CVE-2024-36558/"}