Total DefenseApplication · Broadcom

CVE-2011-1655

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 management.asmx module in the Management Web Service in the Unified Network Control (UNC) Server in CA Total Defense (TD) r12 before SE2 sends a cleartext response to unspecified getDBConfigSettings requests, which makes it easier for remote attackers to obtain database credentials, and subsequently execute arbitrary code, by sniffing the network, related to the UNCWS Web Service.

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

The management.asmx web service in CA Total Defense r12 before SE2 returns cleartext database credentials in response to getDBConfigSettings requests. Attackers can sniff network traffic to capture these credentials and subsequently execute arbitrary code on the affected system.

MitigationEnable TLS/SSL encryption on the UNCWS Management Web Service endpoint to protect responses from being transmitted in cleartext, or upgrade to CA Total Defense r12 SE2 or later which addresses this vulnerability.

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
Total DefenseApplication
Affected:= r12

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
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 checks

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

  1. Verify CA Total Defense r12 is installed
    Check the installed software version through the system control panel, registry, or installed programs list to confirm CA Total Defense r12 is present
    Affected if The product CA Total Defense r12 is installed
  2. Determine the exact patch level
    Check the version/build number of the installed CA Total Defense r12 to see if it is before SE2 (Security Enhancement 2)
    Affected if The version is CA Total Defense r12 base or an earlier patch level prior to the SE2 update
  3. Confirm management.asmx web service is accessible
    Attempt to access the management.asmx web service endpoint (typically at UNCWS/Management/management.asmx) via HTTP on the affected server
    Affected if The management.asmx web service responds to HTTP requests without requiring SSL/TLS
  4. Verify SSL/TLS is not enforced on the web service
    Check the IIS or web server configuration bindings for the UNCWS virtual directory to determine if HTTPS/SSL is not enabled or not enforced
    Affected if The web service endpoint is configured for HTTP only or allows cleartext connections
  5. Capture network traffic to verify cleartext transmission
    Use a network sniffer or packet capture tool on traffic to the management.asmx endpoint to observe if database credentials are transmitted in cleartext
    Affected if Network traffic to the management.asmx service contains readable database credentials without encryption

A user is affected if they have CA Total Defense r12 installed at a version prior to SE2 AND the management.asmx web service is accessible over unencrypted HTTP connections, allowing database credentials to be captured in cleartext network traffic.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable TLS/SSL encryption on the UNCWS Management Web Service endpoint to protect responses from being transmitted in cleartext, or upgrade to CA Total Defense r12 SE2 or later which addresses this vulnerability.

Fix this in Total Defense Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-1655 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