# CVE-2005-2667: Denial of service in n/a

> Attackers can cause a denial of service in CA Message Queuing via unknown vectors on the TCP port.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-694f-8j9w-ggxc

## What is CVE-2005-2667?

CVE-2005-2667 is a medium-severity denial of service vulnerability in n/a, published on 23 Aug 2005. It can be exploited over the network, with no action from the victim.

### Official description

Unknown vulnerability in Computer Associates (CA) Message Queuing (CAM / CAFT) 1.05, 1.07 before Build 220_13, and 1.11 before Build 29_13 allows attackers to cause a denial of service via unknown vectors, aka the "CAM TCP port vulnerability."

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

It affects 24 products.


Products: Broadcom Advantage Data Transport, Broadcom Adviseit, Broadcom Brightstor Portal, Broadcom Brightstor San Manager, Broadcom Cleverpath Ecm, Broadcom Cleverpath Olap, Broadcom Cleverpath Predictive Analysis Server, Broadcom Etrust Admin, Broadcom Message Queuing, Broadcom Unicenter Application Performance Monitor, Broadcom Unicenter Asset Management, Broadcom Unicenter Data Transport Option, Broadcom Unicenter Jasmine, Broadcom Unicenter Performance Management, Broadcom Unicenter Remote Control, Broadcom Unicenter Service Level Management, Broadcom Unicenter Software Delivery, Broadcom Unicenter Tng, Ca Unicenter Asset Management, Ca Unicenter Enterprise Job Manager and 4 more.

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

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

## Is CVE-2005-2667 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2668](https://insights.sbomify.com/CVE-2005-2668/): Memory corruption in n/a (critical 10.0)
- [CVE-2005-2669](https://insights.sbomify.com/CVE-2005-2669/): Command injection in n/a (critical 10.0)
- [CVE-2007-0060](https://insights.sbomify.com/CVE-2007-0060/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2667 is a medium-severity denial of service vulnerability in n/a, published on 23 Aug 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2667 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-2667/ (Markdown: https://insights.sbomify.com/CVE-2005-2667/index.md)
```

## Sources

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

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