{"answers":{"affected":"It affects 5 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2580 exists.","fix":"No fix has been published for CVE-2013-2580 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-2580 is a high-severity vulnerability in n/a, published on 11 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-2580 and fix it if it is affected.\n\nWhat it is: CVE-2013-2580 is a high-severity vulnerability in n/a, published on 11 Oct 2013. 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-2013-2580 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-2013-2580/ (Markdown: https://insights.sbomify.com/CVE-2013-2580/index.md)","id":"CVE-2013-2580","markdown":"https://insights.sbomify.com/CVE-2013-2580/index.md","name":"CVE-2013-2580","record":{"aliases":["GHSA-cf4f-q5h6-h25q"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"IP Camera","requires_auth":"none","summary":"Remote attackers can upload arbitrary files to TP-Link IP cameras via an unrestricted upload endpoint, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lm_firmware","vendor":"tp-link"},{"product":"tl-sc3130","vendor":"tp-link"},{"product":"tl-sc3130g","vendor":"tp-link"},{"product":"tl-sc3171","vendor":"tp-link"},{"product":"tl-sc3171g","vendor":"tp-link"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:C/A:N","version":"2.0"},"cwes":[],"description":"Unrestricted file upload vulnerability in cgi-bin/uploadfile in TP-Link IP Cameras TL-SC3130, TL-SC3130G, TL-SC3171, TL-SC3171G, and possibly other models before beta firmware LM.1.6.18P12_sign6, allows remote attackers to upload arbitrary files, then accessing it via a direct request to the file in the mnt/mtd directory.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2013-08-02","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2013-08-02","kind":"exploitdb","ref":"27289","stars":null,"title":"TP-Link TL-SC3171 IP Cameras - Multiple Vulnerabilities"}],"tier":"weaponised"},"has_fix":null,"headline":"File upload in n/a","id":"CVE-2013-2580","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2013"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2013-2581"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2013-2579"},"products":["n/a"],"published":"2013-10-11","related":[{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2013-2578","kev_date_added":null,"published":"2013-10-11"},{"cvss_score":10,"headline":"Hardcoded credentials in n/a","id":"CVE-2013-2579","kev_date_added":null,"published":"2013-10-11"},{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2013-2581","kev_date_added":null,"published":"2013-10-11"},{"cvss_score":7.1,"headline":"Missing authorization in n/a","id":"CVE-2013-3688","kev_date_added":null,"published":"2013-10-01"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Remote attackers can upload arbitrary files to TP-Link IP cameras via an unrestricted upload endpoint, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2013-2580/"}