CVE-2001-1476 SSH before 2.0, with RC4 encryption and the "disallow NULL passwords" option enabled, makes it easier for remote attackers to guess portions
High 7.5
Published
Updated
Check this codebase for CVE-2001-1476 and fix it if it is affected.
What it is: CVE-2001-1476 is a high-severity vulnerability in n/a, published on 21 Apr 2005.
Exploitation: There is no known exploitation of CVE-2001-1476 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2001-1476/ (Markdown: https://insights.sbomify.com/CVE-2001-1476/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2001-1476?
CVE-2001-1476 is a high-severity vulnerability in n/a, published on 21 Apr 2005.
Official description
SSH before 2.0, with RC4 encryption and the "disallow NULL passwords" option enabled, makes it easier for remote attackers to guess portions of user passwords by replaying user sessions with certain modifications, which trigger different messages depending on whether the guess is correct or not.
Which versions are affected by CVE-2001-1476?
It affects 1 product.
Products include Ssh Ssh.
How do I fix CVE-2001-1476?
No fix has been published for CVE-2001-1476 yet. Limit exposure of the affected software until one is available.
Is CVE-2001-1476 being exploited?
There is no known exploitation of CVE-2001-1476 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-1999-0248 Race condition in n/a
- CVE-1999-0013 Information disclosure in n/a
- CVE-2001-1473 Weak cryptography in n/a
- CVE-2001-1475 SSH before 2.0, when using RC4 and password authentication, allows remote attackers to replay messages until a new server key (VK) is generated.
- CVE-2001-0471 Information disclosure in n/a
Sources
Also known as GHSA-438j-26hg-98wc.