dbcve.org
Single Sign OnApplication · Broadcom

CVE-2015-6854

CRITICAL · 9.1 CVSS v3.0 Published 2016-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The non-Domino web agents in CA Single Sign-On (aka SSO, formerly SiteMinder) R6, R12.0 before SP3 CR13, R12.0J before SP3 CR1.2, and R12.5 before CR5 allow remote attackers to cause a denial of service (daemon crash) or obtain sensitive information via a crafted request.

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 confidence

CA Single Sign-On (formerly SiteMinder) contains a vulnerability in non-Domino web agents where crafted requests can cause the daemon to crash (denial of service) or potentially leak sensitive information. The issue affects versions R6, R12.0 before SP3 CR13, R12.0J before SP3 CR1.2, and R12.5 before CR5.

MitigationApply the vendor-supplied patches: upgrade to R12.0 SP3 CR13 or later, R12.0J SP3 CR1.2 or later, or R12.5 CR5 or later. For R6, contact CA for available fixes.

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
Single Sign OnApplication
Affected:= r6.0= r12.0= r12.0j= r12.5

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the CA SiteMinder/Single Sign-On Policy Server version
    Locate the Policy Server installation and check the version. On Windows, this is often in the registry under HKLM\Software\ComputerAssociates\SiteMinder or check the 'bin\smpolicy' executable version. On Unix, check the installation directory or run 'smpolicy -version' if available.
    Affected if The version falls within: R6 (any), R12.0 before SP3 CR13, R12.0J before SP3 CR1.2, or R12.5 before CR5
  2. Identify the Web Agent version in use
    Check the Web Agent installation on your web servers (IIS, Apache, etc.). The web agent version is typically logged at startup or can be found in the agent configuration files (typically SmAgent.conf or in the web server's module configuration).
    Affected if The Web Agent version corresponds to one of the vulnerable Policy Server versions listed above (R6, R12.0 pre-SP3 CR13, R12.0J pre-SP3 CR1.2, R12.5 pre-CR5)
  3. Confirm the Web Agent type is non-Domino
    Examine the Web Agent configuration files (SmAgent.conf or equivalent) and the web server configuration to determine if the Domino-specific agent module is in use. The vulnerability explicitly affects non-Domino web agents; Domino agents may not be vulnerable.
    Affected if The agent is NOT configured as a Domino web agent - meaning standard SiteMinder web agent is in use, which is the affected configuration

You are affected if you are running any CA Single Sign-On / SiteMinder version R6, R12.0 prior to SP3 CR13, R12.0J prior to SP3 CR1.2, or R12.5 prior to CR5, using non-Domino web agents.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches: upgrade to R12.0 SP3 CR13 or later, R12.0J SP3 CR1.2 or later, or R12.5 CR5 or later. For R6, contact CA for available fixes.

Recommended fix Moderate confidence

R12.0 SP3 CR13, R12.0J SP3 CR1.2, or R12.5 CR5 (or later)

  1. Upgrade CA Single Sign-On R12.0 to Service Pack 3 with CR13 or later
  2. Upgrade CA Single Sign-On R12.0J to Service Pack 3 with CR1.2 or later
  3. Upgrade CA Single Sign-On R12.5 to CR5 or later
  4. For R6.0, contact CA Technologies for available patch options or consider migrating to a supported release
  5. After upgrading, verify the non-Domino web agents are functioning correctly and test for the vulnerability
Caveat Review CA release notes for any compatibility issues or configuration changes required when applying the CR/patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Single Sign On Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6854 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-6854 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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