CVE-2004-1812
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 · uneditedMultiple stack-based buffer overflows in Agent Common Services (1) cam.exe and (2) awservices.exe in Unicenter TNG 2.4 allow remote attackers to execute arbitrary code.
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 vulnerabilities in two Agent Common Services executables (cam.exe and awservices.exe) in CA Unicenter TNG 2.4 allow remote attackers to inject and execute arbitrary code by overflowing stack buffers through specially crafted network requests.
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= 2.4= 2.4.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if CA Unicenter TNG is installedCheck the system for CA Unicenter TNG installation by looking in Program Files for CA or Unicenter directories, or check Windows Services for services starting with 'CA' or 'Unicenter'Affected if CA Unicenter TNG software is found on the system
-
Verify the installed Unicenter TNG versionCheck the version of the Unicenter TNG installation. Common locations: Look in Add/Remove Programs, or check version info on the cam.exe/awservices.exe executables in the TNG installation directory (typically in bin or agent directories)Affected if The installed version is exactly 2.4 or 2.4.2
-
Locate the vulnerable executablesSearch for cam.exe and awservices.exe in the Unicenter TNG installation directory and subdirectories. These are the Agent Common Services executables that contain the vulnerabilityAffected if Both cam.exe and awservices.exe executables are present in the TNG installation
-
Check if vulnerable services are runningOpen Windows Services console (services.msc) and look for CA Unicenter TNG Agent services, or run 'netstat -an' to check if ports associated with these services are listening (commonly port 211 or similar)Affected if The cam.exe or awservices.exe services are running and listening on network ports
-
Determine network exposureReview firewall rules and network configuration to determine if the Unicenter TNG agent services (cam.exe/awservices.exe) are accessible from untrusted networks. Check for open ports that the services useAffected if The vulnerable services are exposed to network access beyond the local subnet or from untrusted hosts
The environment is affected if CA Unicenter TNG version 2.4 or 2.4.2 is installed with the cam.exe or awservices.exe executables present and running, especially if exposed to network access.
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 vendor patches if available; otherwise, upgrade to a supported version of CA Unicenter or implement network segmentation and compensating controls to limit exposure to vulnerable services.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-1812 — 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-2004-1812 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