# CVE-2005-2984: Security feature bypass in n/a

> Authenticated attackers can bypass port restrictions on Avocent CCM console servers via SSH to access serial ports.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g4xj-7rjq-34rj

## What is CVE-2005-2984?

CVE-2005-2984 is a medium-severity vulnerability in n/a, published on 19 Sep 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Avocent CCM console server running firmware 2.1 CCM4850 allows remote authenticated attackers to bypass port restrictions by connecting to the server via SSH and using the connect command to access the serial port.

## Which versions are affected by CVE-2005-2984?

It affects 1 product.


Products: Data Center Resources Avocent.

## How do I fix CVE-2005-2984?

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

## Is CVE-2005-2984 being exploited?

There is no known exploitation of CVE-2005-2984 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2984 and fix it if it is affected.

What it is: CVE-2005-2984 is a medium-severity vulnerability in n/a, published on 19 Sep 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2984 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-2005-2984/ (Markdown: https://insights.sbomify.com/CVE-2005-2984/index.md)
```

## Sources

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

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