{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-17007 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-17007 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-17007 is a medium-severity denial of service vulnerability in n/a, published on 13 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-17007 and fix it if it is affected.\n\nWhat it is: CVE-2018-17007 is a medium-severity denial of service vulnerability in n/a, published on 13 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-17007 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-2018-17007/ (Markdown: https://insights.sbomify.com/CVE-2018-17007/index.md)","id":"CVE-2018-17007","markdown":"https://insights.sbomify.com/CVE-2018-17007/index.md","name":"CVE-2018-17007","record":{"aliases":["GHSA-72gh-xc53-v64g"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"TP-Link wireless router","requires_auth":"low_privilege","summary":"Authenticated attackers can crash router services by sending long JSON data for the wireless SSID, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tl-wr886n_firmware","vendor":"tp-link"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[],"description":"An issue was discovered on TP-Link TL-WR886N 6.0 2.3.4 and TL-WR886N 7.0 1.1.0 devices. Authenticated attackers can crash router services (e.g., inetd, HTTP, DNS, and UPnP) via long JSON data for wireless wlan_wds_2g ssid.","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":"Denial of service in n/a","id":"CVE-2018-17007","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2018-17008"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-17006"},"products":["n/a"],"published":"2018-09-13","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-44622","kev_date_added":null,"published":"2022-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-44623","kev_date_added":null,"published":"2022-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-44625","kev_date_added":null,"published":"2022-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-44626","kev_date_added":null,"published":"2022-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-44627","kev_date_added":null,"published":"2022-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-44628","kev_date_added":null,"published":"2022-03-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-44629","kev_date_added":null,"published":"2022-03-09"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Authenticated attackers can crash router services by sending long JSON data for the wireless SSID, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2018-17007/"}