{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18007 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18007 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18007 is a critical vulnerability in n/a, published on 21 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-18007 and fix it if it is affected.\n\nWhat it is: CVE-2018-18007 is a critical vulnerability in n/a, published on 21 Dec 2018. 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-2018-18007 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-18007/ (Markdown: https://insights.sbomify.com/CVE-2018-18007/index.md)","id":"CVE-2018-18007","markdown":"https://insights.sbomify.com/CVE-2018-18007/index.md","name":"CVE-2018-18007","record":{"aliases":["GHSA-7hr6-6xp5-7xf9"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"D-Link DSL-2770L","requires_auth":"none","summary":"Remote unauthenticated attackers can discover admin credentials via atbox.htm on D-Link DSL-2770L devices, leading to full device compromise.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dsl-2770l_firmware","vendor":"dlink"}],"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":"atbox.htm on D-Link DSL-2770L devices allows remote unauthenticated attackers to discover admin credentials.","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-2018-18007","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2018-18008"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2018-18006"},"products":["n/a"],"published":"2018-12-21","related":[],"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 unauthenticated attackers can discover admin credentials via atbox.htm on D-Link DSL-2770L devices, leading to full device compromise.","url":"https://insights.sbomify.com/CVE-2018-18007/"}