dbcve.org
Output Management Web ViewerApplication · Broadcom

CVE-2011-1719

HIGH · 9.3 CVSS v2.0 Published 2011-04-27
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
Multiple stack-based buffer overflows in the Web Viewer ActiveX controls in CA Output Management Web Viewer 11.0 and 11.5 allow remote attackers to execute arbitrary code via (1) a long SRC property value to the PPSViewer ActiveX control in PPSView.ocx before 1.0.0.7 or (2) a long Title property value to the UOMWV_Helper ActiveX control in UOMWV_HelperActiveX.ocx before 11.5.0.1.

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

Stack-based buffer overflows in CA Output Management Web Viewer's ActiveX controls (PPSView.ocx and UOMWV_HelperActiveX.ocx) allow remote code execution via oversized property values. The PPSViewer control is vulnerable through an overly long SRC property, while the UOMWV_Helper control is vulnerable through an overly long Title property.

MitigationUpgrade PPSView.ocx to version 1.0.0.7 or later and UOMWV_HelperActiveX.ocx to version 11.5.0.1 or later. Alternatively, disable these ActiveX controls in Internet Explorer until patches can be applied.

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
Output Management Web ViewerApplication
Affected:= 11.0= 11.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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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. Locate PPSView.ocx and UOMWV_HelperActiveX.ocx on the system
    Search for these .ocx files in the CA Output Management Web Viewer installation directory (commonly in C:\Program Files\CA\ or C:\Program Files (x86)\CA\) and note their file paths
    Affected if Either .ocx file exists on the system and matches the product installation
  2. Retrieve the version of PPSView.ocx
    Right-click the PPSView.ocx file, select Properties, and check the File Version field on the Details tab. Alternatively, right-click in Windows Explorer, select Properties, then view Version tab
    Affected if Version is earlier than 1.0.0.7
  3. Retrieve the version of UOMWV_HelperActiveX.ocx
    Right-click the UOMWV_HelperActiveX.ocx file, select Properties, and check the File Version field on the Details tab. Alternatively, right-click in Windows Explorer, select Properties, then view Version tab
    Affected if Version is earlier than 11.5.0.1
  4. Check if ActiveX controls are registered in Windows registry
    Open regedit and navigate to HKEY_CLASSES_ROOT\CLSID\ for the following CLSIDs: {6F6A5E60-3AA9-11D4-8A75-8C0411C33B44} (PPSView) and {C44520D5-6A7B-43AB-9DEE-4F6BB2A9C7C2} (UOMWV_Helper) - these are typical CLSIDs for these controls. Verify if they exist under this key
    Affected if Either CLSID is registered, indicating the ActiveX control is installed and available to Internet Explorer
  5. Check if controls are enabled in Internet Explorer
    Open Internet Explorer, go to Tools > Manage Add-ons, and look for 'PPSView' or 'UOMWV_HelperActiveX' in the list of ActiveX controls. Check if they are enabled (not disabled)
    Affected if The controls appear in the enabled state in Internet Explorer add-ons

A system is affected if either PPSView.ocx with version below 1.0.0.7 or UOMWV_HelperActiveX.ocx with version below 11.5.0.1 is present and registered, and the controls are enabled in Internet Explorer, allowing oversized property values to trigger the buffer overflow.

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

Upgrade PPSView.ocx to version 1.0.0.7 or later and UOMWV_HelperActiveX.ocx to version 11.5.0.1 or later. Alternatively, disable these ActiveX controls in Internet Explorer until patches can be applied.

Fix this in Output Management Web Viewer 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-2011-1719 — 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-2011-1719 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