LiveActive security incident?Get immediate response
CVE Record

CVE-2005-2667: Unknown vulnerability in Computer Associates (CA) Message Queuing (CAM / CAFT) 1.05, 1.07 before Build 220_...

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."

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's Takeunknown

Analyst readout for executives and security teams

Plain-English summary

This is an old denial-of-service issue in Computer Associates Message Queuing, also known as CAM or CAFT. Affected builds could be forced to stop providing service through unspecified network-related vectors. The public record does not provide technical detail, CVSS scoring, or evidence of active exploitation.

Executive priority

Treat this as a legacy exposure cleanup item unless CAM/CAFT is business-critical or externally reachable. Prioritize confirming whether the component still exists, then reduce network exposure and update or retire affected installations.

Technical view

CVE-2005-2667 covers an unknown vulnerability in CA Message Queuing CAM/CAFT 1.05, 1.07 before Build 220_13, and 1.11 before Build 29_13. The described impact is denial of service via unknown vectors, named the CAM TCP port vulnerability. No CWE, CVSS vector, or exploit details are provided.

Likely exposure

Exposure is most likely in legacy environments still running CA CAM/CAFT, especially systems tied to older CA management software. Risk depends on whether the CAM TCP service is present, reachable, and running one of the listed vulnerable builds.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Public details are sparse: the vector is unknown, and the documented consequence is denial of service rather than data theft or code execution.

Researcher notes

The public CVE text leaves the attack vector unspecified and provides no CVSS or CWE. Analysis should focus on asset confirmation, build identification, and service reachability. Avoid assuming remote code execution, specific payloads, or active exploitation without additional vendor or threat-intelligence evidence.

Mitigation direction

  • Inventory systems for CA CAM/CAFT installations and exact build numbers.
  • Check CA or successor vendor guidance for the referenced security notice.
  • Upgrade vulnerable 1.07 and 1.11 builds to fixed builds or later supported versions.
  • Disable CAM/CAFT where it is no longer required.
  • Restrict network access to the CAM TCP service to trusted management hosts only.

Validation and detection

  • Confirm whether CAM/CAFT 1.05, 1.07, or 1.11 is installed.
  • Record build numbers and compare them with Build 220_13 and Build 29_13 thresholds.
  • Review firewall and segmentation rules for CAM TCP service exposure.
  • Check logs and monitoring for unexplained CAM/CAFT crashes or service interruptions.
Prepared
Confidence
medium
Sources
6

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2005-2667 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.