{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-0161 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-0161 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-0161 is a medium-severity vulnerability in n/a, published on 14 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2001-0161 and fix it if it is affected.\n\nWhat it is: CVE-2001-0161 is a medium-severity vulnerability in n/a, published on 14 Apr 2005. 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-2001-0161 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-2001-0161/ (Markdown: https://insights.sbomify.com/CVE-2001-0161/index.md)","id":"CVE-2001-0161","markdown":"https://insights.sbomify.com/CVE-2001-0161/index.md","name":"CVE-2001-0161","record":{"aliases":["GHSA-rxqg-33f6-w6r8"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Cisco Aironet AP","requires_auth":"none","summary":"Cisco Aironet access points use insufficient WEP IV bits, allowing remote attackers to easily decrypt traffic via brute force attacks.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"aironet","vendor":"cisco"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"Cisco 340-series Aironet access point using firmware 11.01 does not use 6 of the 24 available IV bits for WEP encryption, which makes it easier for remote attackers to mount brute force attacks.","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":"Weak cryptography in n/a","id":"CVE-2001-0161","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2001"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2001-0162"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2001-0160"},"products":["n/a"],"published":"2005-04-14","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-08","vendors":["n/a"]},"summary":"Cisco Aironet access points use insufficient WEP IV bits, allowing remote attackers to easily decrypt traffic via brute force attacks.","url":"https://insights.sbomify.com/CVE-2001-0161/"}