CVE-2011-2589
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 · uneditedHeap-based buffer overflow in the SendLogAction method in the UUPlayer ActiveX control 6.0.0.1 in UUSee 2010 6.11.0609.2 might allow remote attackers to execute arbitrary code via a long argument.
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 confidenceHeap-based buffer overflow in the SendLogAction method of the UUPlayer ActiveX control (version 6.0.0.1 in UUSee 2010 6.11.0609.2) allows remote attackers to execute arbitrary code by providing an overly long argument, likely overwriting heap metadata to redirect code execution.
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= 6.0.0.1= 2010_6.11.0609.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if UUPlayer ActiveX control is registeredOpen Windows Registry Editor and navigate to HKLM\SOFTWARE\Classes\CLSID\ or HKCU\SOFTWARE\Classes\CLSID\, search for CLSIDs containing 'UUPlayer' or '{6A0E}xxx' patterns typically associated with this ActiveX controlAffected if The UUPlayer ActiveX control CLSID is found in the registry, indicating the vulnerable component is registered on the system
-
Verify the UUPlayer ActiveX control versionLocate the UUPlayer DLL file (typically uuplayer.dll or similar in the UUSee installation directory, commonly in Program Files\UUSee or %SystemRoot%\Downloaded Program Files), right-click the file, select Properties, and check the File Version on the Details tabAffected if The file version is 6.0.0.1, matching the vulnerable version listed in CVE-2011-2589
-
Check for UUSee software installationOpen Control Panel > Programs and Features (or run 'appwiz.cpl'), look for 'UUSee' or 'UUSee 2010' in the installed programs listAffected if UUSee 2010 version 6.11.0609.2 or similar is installed, as this bundles the vulnerable UUPlayer ActiveX control
-
Inspect ActiveX control CLSID in Internet ExplorerOpen Internet Explorer, go to Tools > Manage Add-ons > Enable/Disable Add-ons, look for 'UUPlayer' or 'UUMedia Player' in the list of ActiveX controls and note its CLSID and version if displayedAffected if The UUPlayer ActiveX control appears enabled in Internet Explorer with version 6.0.0.1 or unspecified version on UUSee 2010 systems
A system is affected if the UUPlayer ActiveX control (version 6.0.0.1) or UUSee 2010 (version 6.11.0609.2) is installed and the vulnerable ActiveX component is registered on the system.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable or unregister the vulnerable UUPlayer ActiveX control on affected systems; if a vendor patch is available, apply it; otherwise remove the UUSee 2010 software entirely. Consider network-level controls to block external vectors targeting this ActiveX component.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2589 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-2589 in production — separate from our analysis above.
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.
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.
- 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