{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-10523 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-10523 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-10523 is a medium-severity vulnerability in TP-Link Tapo H100 IoT Smart Hub, published on 4 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-10523 and fix it if it is affected.\n\nWhat it is: CVE-2024-10523 is a medium-severity vulnerability in TP-Link Tapo H100 IoT Smart Hub, published on 4 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-10523 in the wild and no public exploit code.\n\nAffected product: TP-Link Tapo H100 IoT Smart Hub. 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-10523/ (Markdown: https://insights.sbomify.com/CVE-2024-10523/index.md)","id":"CVE-2024-10523","markdown":"https://insights.sbomify.com/CVE-2024-10523/index.md","name":"CVE-2024-10523","record":{"aliases":["GHSA-rhh2-f22c-xh7f"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IoT Smart Hub","requires_auth":"none","summary":"Attackers with physical access can extract Wi-Fi credentials from the device firmware due to plain text storage.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-In","cpe":[{"product":"tapo_h100_firmware","vendor":"tp-link"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"This vulnerability exists in TP-Link IoT Smart Hub due to storage of Wi-Fi credentials in plain text within the device firmware. An attacker with physical access could exploit this by extracting the firmware and analyzing the binary data to obtain the Wi-Fi credentials stored on the vulnerable device.","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 Vulnerability in TP-Link IoT Smart Hub","id":"CVE-2024-10523","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":"GNU Wget is vulnerable to an SSRF attack when accessing partially-user-controlled shorthand URLs","id":"CVE-2024-10524"},"packages":[],"prev":{"headline":"Co-marquage service-public.fr \u003c= 0.5.76 - Reflected Cross-Site Scripting via add_query_arg Parameter","id":"CVE-2024-10522"},"products":["TP-Link Tapo H100 IoT Smart Hub"],"published":"2024-11-04","related":[{"cvss_score":7.5,"headline":"Improper Certificate Validation in TP-Link Tapo H100 and P100 Allows Man-in-the-Middle Attack","id":"CVE-2025-15557","kev_date_added":null,"published":"2026-02-05"}],"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":"2024-11-04","vendors":["TP-Link"]},"summary":"Attackers with physical access can extract Wi-Fi credentials from the device firmware due to plain text storage.","url":"https://insights.sbomify.com/CVE-2024-10523/"}