{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-4835 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-4835 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4835 is a high-severity denial of service vulnerability in n/a, published on 30 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-4835 and fix it if it is affected.\n\nWhat it is: CVE-2005-4835 is a high-severity denial of service vulnerability in n/a, published on 30 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2005-4835 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-2005-4835/ (Markdown: https://insights.sbomify.com/CVE-2005-4835/index.md)","id":"CVE-2005-4835","markdown":"https://insights.sbomify.com/CVE-2005-4835/index.md","name":"CVE-2005-4835","record":{"aliases":["GHSA-4r52-ff3g-g952"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MadWifi driver","requires_auth":"none","summary":"Remote attackers can crash the system via a race condition in the MadWifi driver by moving a connected device to an area with low signal strength.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"madwifi","vendor":"madwifi"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:N/A:C","version":"2.0"},"cwes":[],"description":"The ath_rate_sample function in the ath_rate/sample/sample.c sample code in MadWifi before 0.9.3 allows remote attackers to cause a denial of service (failed KASSERT and system crash) by moving a connected system to a location with low signal strength, and possibly other vectors related to a race condition between interface enabling and packet transmission.","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-2005-4835","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2005"},"n_packages":0,"n_references":8,"next":{"headline":"Apache Tomcat allows remote attackers to read JSP source files","id":"CVE-2005-4836"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2005-4834"},"products":["n/a"],"published":"2007-03-30","related":[{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2007-2831","kev_date_added":null,"published":"2007-05-24"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2006-7177","kev_date_added":null,"published":"2007-03-30"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2006-7178","kev_date_added":null,"published":"2007-03-30"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2006-7179","kev_date_added":null,"published":"2007-03-30"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2006-6332","kev_date_added":null,"published":"2006-12-10"},{"cvss_score":6.8,"headline":"Information disclosure in n/a","id":"CVE-2006-7180","kev_date_added":null,"published":"2007-03-30"}],"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-08","vendors":["n/a"]},"summary":"Remote attackers can crash the system via a race condition in the MadWifi driver by moving a connected device to an area with low signal strength.","url":"https://insights.sbomify.com/CVE-2005-4835/"}