dbcve.org
Advantage Data TransportApplication · Broadcom

CVE-2005-2669

HIGH · 10.0 CVSS v2.0 Published 2005-08-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Computer Associates (CA) Message Queuing (CAM / CAFT) 1.05, 1.07 before Build 220_13, and 1.11 before Build 29_13 allows remote attackers to execute arbitrary commands via spoofed CAFT packets.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CA Message Queuing (CAM/CAFT) versions 1.05, 1.07 before Build 220_13, and 1.11 before Build 29_13 contain a vulnerability allowing remote attackers to execute arbitrary commands by sending spoofed CAFT packets to the message queuing service.

MitigationApply vendor patches to update to CAM/CAFT Build 220_13 (for versions 1.05/1.07) or Build 29_13 (for version 1.11) or later. If patching is not feasible, restrict network access to CAM/CAFT ports at the network perimeter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Advantage Data TransportApplication
Affected:= 3.0
AdviseitApplication
Affected:= 2.4
Brightstor PortalApplication
Affected:= 11.1
Brightstor San ManagerApplication
Affected:= 1.1= 11.1
Cleverpath AionApplication
Affected:= 10.0
Cleverpath EcmApplication
Affected:= 3.5
Cleverpath OlapApplication
Affected:= 5.1
Cleverpath Predictive Analysis ServerApplication
Affected:= 2.0= 3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if CAM/CAFT service is running
    Check for CAM or CAFT processes or services on the system. On Windows, use 'sc query' or check Task Manager for cam.exe, caft.exe, or similar CAM/CAFT processes. On Unix/Linux, use 'ps -ef | grep -i caft' or check for running daemon processes related to CA Message Queuing.
    Affected if CAM/CAFT process or service is running and exposed to network
  2. Determine CAM/CAFT version and build number
    Locate the CAM/CAFT installation directory and check version information. Common locations include CA software directories. Look for version.txt, about.exe, or use 'camq -version' if available. The build number is typically displayed in the version info (for example: Build 220_13 or Build 29_13).
    Affected if Version is 1.05, 1.07 (any build before 220_13), or 1.11 (any build before 29_13)
  3. Check network exposure of CAM/CAFT ports
    Identify which ports CAM/CAFT is listening on (commonly TCP ports in the 4100-4105 range or as configured). Use 'netstat -an | grep <port>' or port scanning tools to determine if these ports are accessible from untrusted networks.
    Affected if CAM/CAFT service ports are accessible from untrusted network segments or the internet
  4. Identify installed Broadcom products containing CAM/CAFT
    Check installed software list for the following products: Advantage Data Transport 3.0, Adviseit 2.4, Brightstor Portal 11.1, Brightstor San Manager 1.1 or 11.1, Cleverpath Aion 10.0, Cleverpath Ecm 3.5, Cleverpath Olap 5.1, Cleverpath Predictive Analysis Server 2.0 or 3.0. Use Windows Add/Remove Programs or system inventory tools.
    Affected if Any of these specific Broadcom product versions are installed and include the vulnerable CAM/CAFT component

The environment is affected if CAM/CAFT is running with version 1.05, 1.07 before Build 220_13, or 1.11 before Build 29_13 (or if any of the listed Broadcom product versions are installed), and the service is network-accessible to untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches to update to CAM/CAFT Build 220_13 (for versions 1.05/1.07) or Build 29_13 (for version 1.11) or later. If patching is not feasible, restrict network access to CAM/CAFT ports at the network perimeter.

Fix this in Advantage Data Transport Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-2669 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-2669 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data