{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-0618 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-0618 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-0618 is a high-severity vulnerability in n/a, published on 27 Jul 2001. 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-2001-0618 and fix it if it is affected.\n\nWhat it is: CVE-2001-0618 is a high-severity vulnerability in n/a, published on 27 Jul 2001. 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-2001-0618 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-0618/ (Markdown: https://insights.sbomify.com/CVE-2001-0618/index.md)","id":"CVE-2001-0618","markdown":"https://insights.sbomify.com/CVE-2001-0618/index.md","name":"CVE-2001-0618","record":{"aliases":["GHSA-46c6-wcjc-4jq6"],"analysis":{"component_type":"network_device","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Wireless Residential Gateway","requires_auth":"none","summary":"Remote attackers can decrypt traffic by deriving the WEP key from the clear-text SSID, requiring users to change default settings.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"orinoco_rg-1000","vendor":"lucent"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Orinoco RG-1000 wireless Residential Gateway uses the last 5 digits of the 'Network Name' or SSID as the default Wired Equivalent Privacy (WEP) encryption key.  Since the SSID occurs in the clear during communications, a remote attacker could determine the WEP key and decrypt RG-1000 traffic.","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-0618","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2001"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2001-0619"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2001-0617"},"products":["n/a"],"published":"2001-07-27","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":"Remote attackers can decrypt traffic by deriving the WEP key from the clear-text SSID, requiring users to change default settings.","url":"https://insights.sbomify.com/CVE-2001-0618/"}