# CVE-2001-1291: Security feature bypass in n/a

> The telnet server lacks lockout mechanisms, allowing attackers to easily brute force credentials and gain unauthorized access to the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9qq6-6qwx-6wrm

## What is CVE-2001-1291?

CVE-2001-1291 is a critical vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The telnet server for 3Com hardware such as PS40 SuperStack II does not delay or disconnect remote attackers who provide an incorrect username or password, which makes it easier to break into the server via brute force password guessing.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: 3com Superstack Ii Ps Hub 40 Firmware.

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

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

## Is CVE-2001-1291 being exploited?

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

Public exploit code:

- 3Com SuperStack II PS Hub 40 - TelnetD Weak Password Protection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1291 is a critical vulnerability in n/a, published on 2 Apr 2003. 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-1291 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-1291/ (Markdown: https://insights.sbomify.com/CVE-2001-1291/index.md)
```

## Sources

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

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