{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-4765 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-4765 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-4765 is a medium-severity denial of service vulnerability in n/a, published on 13 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-4765 and fix it if it is affected.\n\nWhat it is: CVE-2006-4765 is a medium-severity denial of service vulnerability in n/a, published on 13 Sep 2006. 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-2006-4765 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-2006-4765/ (Markdown: https://insights.sbomify.com/CVE-2006-4765/index.md)","id":"CVE-2006-4765","markdown":"https://insights.sbomify.com/CVE-2006-4765/index.md","name":"CVE-2006-4765","record":{"aliases":["GHSA-g2mh-w2pc-px3f"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"NETGEAR wireless router","requires_auth":"none","summary":"Attackers can cause a denial of service on NETGEAR DG834GT routers by sending a long string in the login username field.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dg834gt","vendor":"netgear"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"NETGEAR DG834GT Wireless ADSL router running firmware 1.01.28 allows attackers to cause a denial of service (device hang) via a long string in the username field in the login window.","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-2006-4765","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2006"},"n_packages":0,"n_references":4,"next":{"headline":"Path traversal in n/a","id":"CVE-2006-4766"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2006-4764"},"products":["n/a"],"published":"2006-09-13","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Attackers can cause a denial of service on NETGEAR DG834GT routers by sending a long string in the login username field.","url":"https://insights.sbomify.com/CVE-2006-4765/"}