{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49515 exists.","fix":"No fix has been published for CVE-2023-49515 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-49515 is a medium-severity vulnerability in n/a, published on 17 Jan 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-2023-49515 and fix it if it is affected.\n\nWhat it is: CVE-2023-49515 is a medium-severity vulnerability in n/a, published on 17 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49515 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-2023-49515/ (Markdown: https://insights.sbomify.com/CVE-2023-49515/index.md)","id":"CVE-2023-49515","markdown":"https://insights.sbomify.com/CVE-2023-49515/index.md","name":"CVE-2023-49515","record":{"aliases":["GHSA-983x-5446-qc2q"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link WiFi Camera","requires_auth":"none","summary":"A physically proximate attacker can obtain sensitive information by connecting to UART pins on TP-Link cameras due to insecure permissions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tapo_c200_firmware","vendor":"tp-link"},{"product":"tapo_tc70_firmware","vendor":"tp-link"}],"cvss":{"score":4.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"Insecure Permissiosn vulnerability in TP Link TC70 and C200 WIFI Camera v.3 firmware v.1.3.4 and fixed in v.1.3.11 allows a physically proximate attacker to obtain sensitive information via a connection to the UART pin components.","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":"Information disclosure in n/a","id":"CVE-2023-49515","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-49528"},"packages":[],"prev":{"headline":"YetiForceCRM Directory Traversal vulnerability","id":"CVE-2023-49508"},"products":["n/a"],"published":"2024-01-17","related":[{"cvss_score":9.8,"headline":"TP-LINK Tapo C200 remote code execution vulnerability","id":"CVE-2021-4045","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":8.7,"headline":"Unauthenticated Access to connectAP API Endpoint on Tapo C100, C200 \u0026 C425","id":"CVE-2025-14300","kev_date_added":null,"published":"2025-12-20"},{"cvss_score":8.7,"headline":"Remote Code Execution via Stack-based Buffer Overflow in ONVIF SOAP Parser in TP-Link Tapo C200 and C520WS","id":"CVE-2025-8065","kev_date_added":null,"published":"2025-12-20"},{"cvss_score":7.1,"headline":"Denial-of-Service via Oversized Encrypted Credential Input in TP-Link Tapo C200","id":"CVE-2026-15316","kev_date_added":null,"published":"2026-08-18"},{"cvss_score":7.1,"headline":"Denial-of-Service Vulnerability via Malformed IPv4 Fragmentation Handling in TP-Link Tapo C200","id":"CVE-2026-12760","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":7.1,"headline":"Authenticated Stack-based Buffer Overflow in RTSP Authentication of Tapo C200","id":"CVE-2026-1871","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":7.1,"headline":"Improper Content-Length Validation in HTTPS Requests on Tapo C200","id":"CVE-2025-14299","kev_date_added":null,"published":"2025-12-20"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"A physically proximate attacker can obtain sensitive information by connecting to UART pins on TP-Link cameras due to insecure permissions.","url":"https://insights.sbomify.com/CVE-2023-49515/"}