{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8078 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8078 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8078 is a medium-severity missing authorization vulnerability in n/a, published on 23 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-8078 and fix it if it is affected.\n\nWhat it is: CVE-2017-8078 is a medium-severity missing authorization vulnerability in n/a, published on 23 Apr 2017. 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-2017-8078 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-2017-8078/ (Markdown: https://insights.sbomify.com/CVE-2017-8078/index.md)","id":"CVE-2017-8078","markdown":"https://insights.sbomify.com/CVE-2017-8078/index.md","name":"CVE-2017-8078","record":{"aliases":["GHSA-7qvq-87r6-ph4c"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"TP-Link network switch","requires_auth":"none","summary":"Remote attackers can trigger firmware upgrades without authentication on TP-Link TL-SG108E switches, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tl-sg108e_firmware","vendor":"tp-link"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"On the TP-Link TL-SG108E 1.0, the upgrade process can be requested remotely without authentication (httpupg.cgi with a parameter called cmd). This affects the 1.1.2 Build 20141017 Rel.50749 firmware.","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":"Missing authorization in n/a","id":"CVE-2017-8078","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2017-8080"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2017-8077"},"products":["n/a"],"published":"2017-04-23","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2017-8074","kev_date_added":null,"published":"2017-04-23"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2017-8075","kev_date_added":null,"published":"2017-04-23"},{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2017-8076","kev_date_added":null,"published":"2017-04-23"},{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2017-8077","kev_date_added":null,"published":"2017-04-23"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2017-17746","kev_date_added":null,"published":"2017-12-20"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2017-17747","kev_date_added":null,"published":"2017-12-20"},{"cvss_score":6.3,"headline":"TP-Link TL-SG108E HTTP GET Request usr_account_set.cgi get request method with sensitive query strings","id":"CVE-2025-0730","kev_date_added":null,"published":"2025-01-27"}],"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-05","vendors":["n/a"]},"summary":"Remote attackers can trigger firmware upgrades without authentication on TP-Link TL-SG108E switches, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2017-8078/"}