CVE-2006-6641
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 · uneditedUnspecified vulnerability in CA CleverPath Portal before maintenance version 4.71.001_179_060830, as used in multiple products including BrightStor Portal r11.1, CleverPath Aion BPM r10 through r10.2, eTrust Security Command Center r1 and r8, and Unicenter, does not properly handle when multiple Portal servers are started at the same time and share the same data store, which might cause a Portal user to inherit the session and credentials of a user who is on another Portal server.
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 confidenceThis is a session hijacking vulnerability in CA CleverPath Portal where improper handling of concurrent server startup with shared data store causes users to inherit sessions and credentials from users on other Portal servers. The race condition in multi-server environments leads to authentication bypass through session credential leakage.
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= 11.1<= 4.71= r10= r10.1= r10.2= r4.7= r4.51= r4.71= r1= r8= r11= r11.1= r11CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 installed CA/Broadcom portal productCheck installed programs or run: ls /opt/CA (Linux) or look in Add/Remove Programs (Windows) for CA CleverPath Portal, Broadcom Cleverpath Portal, Arcserve Brightstor, Cleverpath Aion BPM, Etrust Security Command Center, Unicenter Asset and Portfolio Management, Unicenter Database Command Center, or Unicenter Database Management PortalAffected if Any of these products are installed and match version 11.1, r1, r8, r10, r10.1, r10.2, r4.7, r4.51, r4.71, r11, or r11.1
-
Verify product versionCheck the exact version of the installed product - for Portal check portal version in admin console or registry/config files; for Brightstor check in ARCServe backup manager > About; for Unicenter check in the respective management consoleAffected if Version matches: Broadcom Cleverpath Portal <= 4.71, Cleverpath Portal r4.7/r4.51/r4.71, Cleverpath Aion BPM r10/r10.1/r10.2, Arcserve Brightstor 11.1, Etrust Security Command Center r1/r8, Unicenter Asset and Portfolio Management r11, Unicenter Database Command Center r11.1, Unicenter Database Mana
-
Determine if multi-server deployment existsCheck if multiple portal/application servers are configured to use the same shared data store or database - look at configuration files (e.g., portal.properties, config.xml) for shared database connection strings, or check clustering/multiple node configurations in the admin consoleAffected if Multiple portal servers are configured to start concurrently sharing the same session store or database
-
Check for session isolation configurationReview session management configuration in the web application deployment descriptor (web.xml) and portal configuration files for session timeout, session fixation protection, and whether separate session stores are used per server nodeAffected if Configuration shows shared session storage across servers without proper isolation or the session handling lacks unique identifiers per server startup instance
You are affected if you have any of the listed products installed at the specified versions AND operate in a multi-server deployment with concurrent startup using a shared data store.
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 CA CleverPath Portal maintenance version 4.71.001_179_060830 or later, which contains the fix for proper session isolation in multi-server deployments.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6641 — 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-2006-6641 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