# CVE-2001-0471: Information disclosure in n/a

> SSH daemon version 1 fails to log repeated login attempts, allowing remote attackers to perform undetected brute force attacks to compromise accounts.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xgxx-52g8-m9j3

## What is CVE-2001-0471?

CVE-2001-0471 is a high-severity vulnerability in n/a, published on 24 May 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SSH daemon version 1 (aka SSHD-1 or SSH-1) 1.2.30 and earlier does not log repeated login attempts, which could allow remote attackers to compromise accounts without detection via a brute force attack.

## Which versions are affected by CVE-2001-0471?

It affects 1 product.


Products: Ssh Ssh.

## How do I fix CVE-2001-0471?

No fix has been published for CVE-2001-0471 yet. Limit exposure of the affected software until one is available.

## Is CVE-2001-0471 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-0471 exists.

Public exploit code:

- SSH 1.2.30 - Daemon Logging Failure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-1999-0248](https://insights.sbomify.com/CVE-1999-0248/): Race condition in n/a (critical 10.0)
- [CVE-1999-0013](https://insights.sbomify.com/CVE-1999-0013/): Information disclosure in n/a (high 8.4)
- [CVE-2001-1473](https://insights.sbomify.com/CVE-2001-1473/): Weak cryptography in n/a (high 7.5)
- [CVE-2001-1475](https://insights.sbomify.com/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. (high 7.5)
- [CVE-2001-1476](https://insights.sbomify.com/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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0471 and fix it if it is affected.

What it is: CVE-2001-0471 is a high-severity vulnerability in n/a, published on 24 May 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-0471 exists.

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-0471/ (Markdown: https://insights.sbomify.com/CVE-2001-0471/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2001-0471
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2001-0471
- OSV: https://osv.dev/vulnerability/CVE-2001-0471

---
From sbomify Insights: https://insights.sbomify.com/CVE-2001-0471/
Summaries are generated and may contain mistakes; the official description above is the record.