dbcve.org
Single Sign OnApplication · Broadcom

CVE-2015-6853

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 Domino web agent in CA Single Sign-On (aka SSO, formerly SiteMinder) R6, R12.0 before SP3 CR13, R12.0J before SP3 CR1.2, R12.5 before CR5, R12.51 before CR4, and R12.52 before SP1 CR3 allows 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 · moderate confidence

The vulnerability exists in the Domino web agent component of CA Single Sign-On (formerly SiteMinder). A remote attacker can send a crafted request to trigger either a denial of service (causing the daemon to crash) or unauthorized disclosure of sensitive information. The flaw affects multiple version branches from R6 through R12.52.

MitigationApply the vendor-supplied patches: R12.0 to SP3 CR13, R12.0J to SP3 CR1.2, R12.5 to CR5, R12.51 to CR4, and R12.52 to SP1 CR3 or later. Restrict external access to the Domino web agent endpoints as an interim measure.

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= r12.51= r12.52

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 CA Single Sign-On installation
    Locate the CA Single Sign-On (formerly SiteMinder) installation directory and identify the installed components. Check for the presence of the Domino web agent binaries or configuration files.
    Affected if CA Single Sign-On is installed and the Domino web agent component is present on the system
  2. Determine the installed version
    Query the installed version of CA Single Sign-On using the vendor's version reporting tool or check the product's About information. Compare the version string to the affected versions: r6.0, r12.0, r12.0j, r12.5, r12.51, or r12.52.
    Affected if The installed version matches any of the affected version numbers listed in the CVE
  3. Verify Domino web agent is enabled
    Check the CA Single Sign-On configuration files or administrative console to determine whether the Domino web agent component is enabled and configured for web requests.
    Affected if The Domino web agent is enabled and actively handling web requests
  4. Inspect Domino web agent endpoint exposure
    Review network configuration and the web agent's policy server settings to identify if Domino web agent endpoints are exposed to external network access.
    Affected if Domino web agent endpoints are accessible from external or untrusted networks

A system is affected if it runs any of the affected CA Single Sign-On versions (r6.0, r12.0, r12.0j, r12.5, r12.51, r12.52) with the Domino web agent component enabled and exposed to network requests.

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: R12.0 to SP3 CR13, R12.0J to SP3 CR1.2, R12.5 to CR5, R12.51 to CR4, and R12.52 to SP1 CR3 or later. Restrict external access to the Domino web agent endpoints as an interim measure.

Recommended fix High confidence

R12.0 SP3 CR13 / R12.0J SP3 CR1.2 / R12.5 CR5 / R12.51 CR4 / R12.52 SP1 CR3 (or later supported releases)

  1. Identify your current CA Single Sign-On version by checking the SmSsoVersion file or the admin UI
  2. For r12.0 customers: Upgrade to R12.0 SP3 CR13 or later
  3. For r12.0J customers: Upgrade to R12.0J SP3 CR1.2 or later
  4. For r12.5 customers: Upgrade to R12.5 CR5 or later
  5. For r12.51 customers: Upgrade to R12.51 CR4 or later
  6. For r12.52 customers: Upgrade to R12.52 SP1 CR3 or later
  7. If running r6.0, migrate to a supported release (r12.0 SP3 CR13 or later) as r6.0 is end-of-life
  8. After upgrade, verify the Domino web agent is functioning correctly and test for normal authentication flows
Caveat Review CA support documentation for any configuration changes required between your current version and the target patch level; some older policy store configurations may need migration

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6853 — 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-6853 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