CVE-2011-2590
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 · uneditedThe Play method in the UUPlayer ActiveX control 6.0.0.1 in UUSee 2010 6.11.0609.2 allows remote attackers to execute arbitrary programs via a UNC share pathname in the MPlayerPath parameter.
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 confidenceThe UUPlayer ActiveX control (version 6.0.0.1) in UUSee 2010 contains a vulnerability in its Play method. The MPlayerPath parameter accepts a UNC share pathname without proper validation, allowing remote attackers to specify an arbitrary executable on a remote SMB share that will be executed on the target system.
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 UUSee 2010 software is installedOpen Programs and Features (appwiz.cpl) or check the installation directory for UUSee, typically found in C:\Program Files\UUSee or C:\Program Files (x86)\UUSeeAffected if UUSee 2010 is present on the system
-
Verify the installed UUSee versionRight-click the UUSee executable or DLL (such as UUPlayer.dll) in the installation folder, select Properties, and check the File Version field. Alternatively, check the version in the Programs and Features entryAffected if Version equals 6.0.0.1 for the ActiveX control or 2010_6.11.0609.2 for the UUSee application
-
Locate the UUPlayer ActiveX control CLSID in the registrySearch the Windows Registry under HKEY_CLASSES_ROOT\CLSID for entries containing 'UUPlayer' or look for the component's CLSID registered under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units or in the browser's ActiveX control listsAffected if A CLSID for UUPlayer ActiveX control is registered on the system
-
Confirm the Play method is accessibleUse a tool like OLEVIEW or examine the ActiveX control's type library to verify the Play method with MPlayerPath parameter exists and is marked as safe for scriptingAffected if The vulnerable Play method accepting MPlayerPath parameter is exposed and accessible via Internet Explorer or other browsers
A user is affected if UUSee 2010 version 2010_6.11.0609.2 or the UUPlayer ActiveX control version 6.0.0.1 is installed with the vulnerable Play method available in 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 dataSet the Kill Bit for the vulnerable UUPlayer ActiveX control CLSID in the Windows Registry to disable the control, or remove UUSee 2010 entirely if no patched version is available.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2590 — 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-2590 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