CVE-2004-0425
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 · uneditedHeap-based buffer overflow in SiteMinder Affiliate Agent 4.x allows remote attackers to execute arbitrary code via a large SMPROFILE cookie.
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 confidenceHeap-based buffer overflow in SiteMinder Affiliate Agent 4.x allows remote attackers to execute arbitrary code via a specially crafted large SMPROFILE cookie, leading to complete system compromise.
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= 4.0CVSS 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.
-
Verify SiteMinder Affiliate Agent installationCheck for the presence of SiteMinder Affiliate Agent software on the system. Look for installation directories such as C:\Program Files\Netegrity\SiteMinder or /opt/netegrity/siteminder, or check Windows registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity for the product.Affected if SiteMinder Affiliate Agent version 4.0 is installed on the system.
-
Confirm installed versionLocate the version information for the installed SiteMinder Affiliate Agent. Check the product's About dialog, readme files, or query the Windows registry for the exact version number under the product's installation key.Affected if The installed version is confirmed to be 4.0 or falls within the 4.x product line.
-
Check if Affiliate Agent service is runningVerify whether the SiteMinder Affiliate Agent service is active. On Windows, use Services console or 'sc query' command. On Unix, check running processes for smaffiliate or similar daemon processes.Affected if The SiteMinder Affiliate Agent service is currently running and accepting connections.
-
Inspect SMPROFILE cookie handling configurationReview the SiteMinder Affiliate Agent configuration files (typically .conf or .xml files in the installation directory) for settings related to cookie processing, particularly the SMPROFILE cookie and any size limits or validation settings.Affected if The configuration allows unrestricted or unvalidated SMPROFILE cookie values without proper length limits.
The environment is affected if SiteMinder Affiliate Agent version 4.0 is installed and the service is running, accepting SMPROFILE cookies without adequate size validation.
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 dataUpgrade to a patched version of SiteMinder or migrate to a supported solution, as version 4.x is end-of-life; implement web application firewall rules to block abnormally large cookies as an interim measure.
- 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-0425 — 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-0425 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