{"answers":{"affected":"It affects 7 products.","exploited":"There is no known exploitation of CVE-2020-12110 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-12110 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-12110 is a critical vulnerability in n/a, published on 4 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-12110 and fix it if it is affected.\n\nWhat it is: CVE-2020-12110 is a critical vulnerability in n/a, published on 4 May 2020. 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-2020-12110 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-2020-12110/ (Markdown: https://insights.sbomify.com/CVE-2020-12110/index.md)","id":"CVE-2020-12110","markdown":"https://insights.sbomify.com/CVE-2020-12110/index.md","name":"CVE-2020-12110","record":{"aliases":["GHSA-pq76-49rr-hg9x"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TP-Link IP Camera","requires_auth":"none","summary":"Attackers can exploit hardcoded encryption keys in TP-Link IP cameras to bypass security controls and access sensitive data.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nc200_firmware","vendor":"tp-link"},{"product":"nc210_firmware","vendor":"tp-link"},{"product":"nc220_firmware","vendor":"tp-link"},{"product":"nc230_firmware","vendor":"tp-link"},{"product":"nc250_firmware","vendor":"tp-link"},{"product":"nc260_firmware","vendor":"tp-link"},{"product":"nc450_firmware","vendor":"tp-link"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Certain TP-Link devices have a Hardcoded Encryption Key. This affects NC200 2.1.9 build 200225, N210 1.0.9 build 200304, NC220 1.3.0 build 200304, NC230 1.3.0 build 200304, NC250 1.3.0 build 200304, NC260 1.5.2 build 200304, and NC450 1.5.3 build 200304.","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":"Hardcoded credentials in n/a","id":"CVE-2020-12110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2020-12111"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2020-12109"},"products":["n/a"],"published":"2020-05-04","related":[{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2020-13224","kev_date_added":null,"published":"2020-06-17"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2020-12109","kev_date_added":null,"published":"2020-05-04"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2020-10231","kev_date_added":null,"published":"2020-04-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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can exploit hardcoded encryption keys in TP-Link IP cameras to bypass security controls and access sensitive data.","url":"https://insights.sbomify.com/CVE-2020-12110/"}