{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-1469 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-1469 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-1469 is a medium-severity vulnerability in n/a, published on 21 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-1469 and fix it if it is affected.\n\nWhat it is: CVE-2001-1469 is a medium-severity vulnerability in n/a, published on 21 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-1469 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-1469/ (Markdown: https://insights.sbomify.com/CVE-2001-1469/index.md)","id":"CVE-2001-1469","markdown":"https://insights.sbomify.com/CVE-2001-1469/index.md","name":"CVE-2001-1469","record":{"aliases":["GHSA-p383-6r42-q3rv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SSH protocol","requires_auth":"none","summary":"Remote attackers can modify SSH1 messages without detection due to a flaw in the RC4 stream cipher's CRC handling.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ssh","vendor":"ssh"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"The RC4 stream cipher as used by SSH1 allows remote attackers to modify messages without detection by XORing the original message's cyclic redundancy check (CRC) with the CRC of a mask consisting of all the bits of the original message that were modified.","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-1469","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":"Weak cryptography in n/a","id":"CVE-2001-1470"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2001-1468"},"products":["n/a"],"published":"2005-04-21","related":[{"cvss_score":10,"headline":"Race condition in n/a","id":"CVE-1999-0248","kev_date_added":null,"published":"2000-10-13"},{"cvss_score":8.4,"headline":"Information disclosure in n/a","id":"CVE-1999-0013","kev_date_added":null,"published":"1999-09-29"},{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2001-1473","kev_date_added":null,"published":"2005-04-21"},{"cvss_score":7.5,"headline":"SSH before 2.0, when using RC4 and password authentication, allows remote attackers to replay messages until a new server key (VK) is generated.","id":"CVE-2001-1475","kev_date_added":null,"published":"2005-04-21"},{"cvss_score":7.5,"headline":"SSH before 2.0, with RC4 encryption and the \"disallow NULL passwords\" option enabled, makes it easier for remote attackers to guess portions","id":"CVE-2001-1476","kev_date_added":null,"published":"2005-04-21"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2001-0471","kev_date_added":null,"published":"2001-05-24"},{"cvss_score":7.5,"headline":"SSH 1.2.25 on HP-UX allows access to new user accounts.","id":"CVE-1999-0310","kev_date_added":null,"published":"1999-09-29"}],"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 modify SSH1 messages without detection due to a flaw in the RC4 stream cipher's CRC handling.","url":"https://insights.sbomify.com/CVE-2001-1469/"}