Total DefenseApplication · Broadcom

CVE-2011-1653

HIGH · 10.0 CVSS v2.0 Published 2011-04-18

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

High EPSS Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Multiple SQL injection vulnerabilities in the Unified Network Control (UNC) Server in CA Total Defense (TD) r12 before SE2 allow remote attackers to execute arbitrary SQL commands via vectors involving the (1) UnAssignFunctionalRoles, (2) UnassignAdminRoles, (3) DeleteFilter, (4) NonAssignedUserList, (5) DeleteReportLayout, (6) DeleteReports, and (7) RegenerateReport stored procedures.

Technical summary

dbcve analysis · high confidence

Multiple SQL injection vulnerabilities exist in CA Total Defense r12 Unified Network Control (UNC) Server before SE2. Seven stored procedures (UnAssignFunctionalRoles, UnassignAdminRoles, DeleteFilter, NonAssignedUserList, DeleteReportLayout, DeleteReports, and RegenerateReport) accept unsanitized user input, allowing remote attackers to inject and execute arbitrary SQL commands.

MitigationApply vendor patch SE2 or later for CA Total Defense r12. If patching is delayed, restrict network access to the UNC Server and implement input validation on the identified stored procedures.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Total DefenseApplication

Affected:= r12

CVSS breakdown

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?

dbcve checks

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

Confirm CA Total Defense UNC Server is installed

Check for CA Total Defense Unified Network Control Server installation on the system. Look for the UNC Server component in Add/Remove Programs or check for UNC-related services in Windows Services.

Affected if The product is not found or only non-UNC components are installed, the system is not affected by this specific vulnerability.
Identify the exact version of UNC Server

Check the installed version of CA Total Defense r12 Unified Network Control Server. This may be visible in the program properties, about dialog, or registry keys under the CA installation directory.

Affected if If the version shows r12 without any patch level indicated, assume it may be the base r12 release and potentially affected.
Determine if SE2 patch is applied

Look for patch level information. Check the UNC Server about section, installation logs, or patch inventory for evidence of SE2 patch installation.

Affected if If SE2 patch is not installed or the patch level cannot be confirmed, the system may be vulnerable to the SQL injection flaws in the seven stored procedures.
Verify UNC Server network accessibility

Determine if the UNC Server is running and listening on network ports. Check if the server is accessible remotely or if it accepts connections from non-localhost sources.

Affected if If the UNC Server is exposed to the network without compensating controls, the SQL injection vulnerabilities could be exploited remotely.

If CA Total Defense r12 Unified Network Control Server is installed without the SE2 patch applied and the UNC Server service is running and accessible, the environment is affected by CVE-2011-1653.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply vendor patch SE2 or later for CA Total Defense r12. If patching is delayed, restrict network access to the UNC Server and implement input validation on the identified stored procedures.

Fix this in Total Defense Scoped from the published advisory

Consultation6.0 h
Implementation16.0 h
Testing10.0 h
Review / QA4.0 h

36.0 hours of engineering $6,300

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2011-1653?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 88.7%

Affects: Total Defense

Remediation

A high-priority fix

Fix this in Total Defense 36 hrs · Moderate

Typical engagement from $6,300

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2011-1653 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References