Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2011-1718: The Web Agents component in CA SiteMinder R6 before SP6 CR2 and R12 before SP3 CR2 does not properly handle mu

36
Routine
MEDIUM 4.3DOWNGRADEDOWNGRADE

CVE-2011-1718 is a medium-severity flaw (CVSS 4.3) affecting siteminder, siteminder. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Web Agents component in CA SiteMinder R6 before SP6 CR2 and R12 before SP3 CR2 does not properly handle multi-line headers, which allows remote authenticated users to conduct impersonation attacks and gain privileges via crafted data.

Why this priority

  • No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score4.3 (Medium)
EPSS exploit chance2.4% (top 16%)
CISA exploited listNo
WeaknessCWE-20
Published2011-04-27
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: broadcom · ca

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

broadcom siteminder DOWNGRADE
Affected: 12.0 sp3
Fixed in: no fixed release known
Safe to downgrade to: a release before 12.0
1. Check installed version
apt-cache policy siteminder || rpm -q siteminder || siteminder --version
2. No fixed release: DOWNGRADE to a release before 12.0 (Debian / Ubuntu)
apt-cache madison siteminder sudo apt install siteminder=<VERSION_BEFORE_12.0> sudo apt-mark hold siteminder
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list siteminder sudo dnf downgrade siteminder-<VERSION_BEFORE_12.0> sudo dnf versionlock add siteminder
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
ca siteminder DOWNGRADE
Affected: 6 sp5_cr35
Fixed in: no fixed release known
Safe to downgrade to: a release before 6
1. Check installed version
apt-cache policy siteminder || rpm -q siteminder || siteminder --version
2. No fixed release: DOWNGRADE to a release before 6 (Debian / Ubuntu)
apt-cache madison siteminder sudo apt install siteminder=<VERSION_BEFORE_6> sudo apt-mark hold siteminder
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list siteminder sudo dnf downgrade siteminder-<VERSION_BEFORE_6> sudo dnf versionlock add siteminder
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2011-1718?

siteminder: downgrade or apply the listed mitigation; siteminder: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2011-1718 being exploited?

CVE-2011-1718 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2011-1718 affect?

CVE-2011-1718 affects siteminder, siteminder. Severity is medium (CVSS 4.3). The Web Agents component in CA SiteMinder R6 before SP6 CR2 and R12 before SP3 CR2 does not properly handle multi-line headers, which allows remote authenticated users to conduct impersonation attacks and gain privileges via crafted data.

How urgent is CVE-2011-1718?

Priority 36/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.