# CVE-2001-0564: Denial of service in n/a

> Remote attackers can cause denial of service on APC Web/SNMP Management Cards by exhausting the single telnet connection slot via failed logins.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 9 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-95p5-v3v8-7826

## What is CVE-2001-0564?

CVE-2001-0564 is a medium-severity denial of service vulnerability in n/a, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

APC Web/SNMP Management Card prior to Firmware 310 only supports one telnet connection, which allows a remote attacker to create a denial of service via repeated failed logon attempts which temporarily locks the card.

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

It affects 1 product.


Products: Apc Ap9606.

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

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

## Is CVE-2001-0564 being exploited?

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

Public exploit code:

- APC WEB/SNMP Management Card (9606) Firmware 3.0 - Telnet Administration Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-0311](https://insights.sbomify.com/CVE-2004-0311/): Hardcoded credentials in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0564 is a medium-severity denial of service vulnerability in n/a, published on 9 Mar 2002. 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-0564 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-0564/ (Markdown: https://insights.sbomify.com/CVE-2001-0564/index.md)
```

## Sources

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

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