CVE-2007-0060
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 · uneditedStack-based buffer overflow in the Message Queuing Server (Cam.exe) in CA (formerly Computer Associates) Message Queuing (CAM / CAFT) software before 1.11 Build 54_4 on Windows and NetWare, as used in CA Advantage Data Transport, eTrust Admin, certain BrightStor products, certain CleverPath products, and certain Unicenter products, allows remote attackers to execute arbitrary code via a crafted message to TCP port 3104.
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 · high confidenceStack-based buffer overflow vulnerability in the CA Message Queuing Server (Cam.exe) listening on TCP port 3104. Remote attackers can send specially crafted messages to overflow a stack buffer and execute arbitrary code with elevated privileges.
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= 3.0= 11.1= 11.1= 11.5= 10.0= 3.5= 5.1= 2.0= 3.0= 8.0= 8.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 checksWork through these to decide whether this CVE applies to you.
-
Verify if CAM service is runningCheck running processes for Cam.exe or the CAM service using Task Manager (Processes tab) or command: tasklist /FI "IMAGENAME eq Cam.exe"Affected if Cam.exe process is running on the system
-
Confirm TCP port 3104 is listeningRun command: netstat -ano | findstr :3104 or use: netsh interface tcp show global | findstr 3104 to check if the CAM listener port is openAffected if TCP port 3104 is in LISTENING state and bound to Cam.exe
-
Identify the installed Broadcom/CA product and versionCheck Add/Remove Programs (Windows) or the product's About/Version dialog for the specific Broadcom product installed. Look for: Advantage Data Transport, Brightstor Portal, Brightstor San Manager, Cleverpath Aion, Cleverpath Ecm, Cleverpath Olap, Cleverpath Predictive Analysis Server, or Etrust AdminAffected if Any of the listed products are installed at versions 3.0, 11.1, 11.5, 10.0, 3.5, 5.1, 2.0, 8.0, or 8.1
-
Locate Cam.exe and verify versionLocate Cam.exe in the product installation directory (commonly under C:\Program Files\CA\ or product-specific paths) and check file properties for version information, or use: wmic product get name,versionAffected if Cam.exe version matches the vulnerable product versions listed in the affected products
If the CAM service (Cam.exe) is running, TCP port 3104 is exposed, and the installed product version matches any of the specific versions listed (3.0, 11.1, 11.5, 10.0, 3.5, 5.1, 2.0, 3.0, 8.0, 8.1), the system is vulnerable to remote code execution via stack buffer overflow.
Generated from the published advisory. Verify against your own configuration.
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 dataApply CA CAM/CAFT update to version 1.11 Build 54_4 or later. Until patched, block TCP port 3104 at network perimeter or disable the CAM service if not required.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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