{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-59447 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59447 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59447 is a low-severity vulnerability in YoSmart YoLink Smart Hub, published on 6 Oct 2025. 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-2025-59447 and fix it if it is affected.\n\nWhat it is: CVE-2025-59447 is a low-severity vulnerability in YoSmart YoLink Smart Hub, published on 6 Oct 2025. 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-2025-59447 in the wild and no public exploit code.\n\nAffected product: YoSmart YoLink 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-2025-59447/ (Markdown: https://insights.sbomify.com/CVE-2025-59447/index.md)","id":"CVE-2025-59447","markdown":"https://insights.sbomify.com/CVE-2025-59447/index.md","name":"CVE-2025-59447","record":{"aliases":["GHSA-8fpc-w65m-53qw"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Smart Hub","requires_auth":"none","summary":"Attackers with physical access can read boot logs via UART to obtain network credentials, exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":2.2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-497","name":"Exposure of Sensitive System Information to an Unauthorized Control Sphere"}],"description":"The YoSmart YoLink Smart Hub device 0382 exposes a UART debug interface. An attacker with direct physical access can leverage this interface to read a boot log, which includes network access credentials.","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 YoLink Smart Hub","id":"CVE-2025-59447","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in YoLink ecosystem","id":"CVE-2025-59448"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-59440"},"products":["YoLink Smart Hub"],"published":"2025-10-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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-06","vendors":["YoSmart"]},"summary":"Attackers with physical access can read boot logs via UART to obtain network credentials, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2025-59447/"}