CVE-2011-3006
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 MyAsUtil ActiveX control in MyAsUtil5.2.0.603.dll in McAfee SaaS Endpoint Protection 5.2.1 and earlier allows remote attackers to bypass the MyASUtil.SecureObjectFactory.CreateSecureObject domain execution policy using a cross-site scripting (XSS) attack, execute arbitrary code using the MyASUtil.InstallInfo.RunUserProgram function, and possibly conduct other unspecified attacks.
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 MyAsUtil ActiveX control in McAfee SaaS Endpoint Protection 5.2.1 and earlier contains a vulnerability allowing remote attackers to bypass domain execution policies via XSS attacks and execute arbitrary code through the MyASUtil.InstallInfo.RunUserProgram function.
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<= 5.2.1CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 checksWork through these to decide whether this CVE applies to you.
-
Verify McAfee SaaS Endpoint Protection installation and versionOpen Programs and Features (or run 'wmic product get name,version' from command prompt) and look for 'McAfee SaaS Endpoint Protection' or 'McAfee Endpoint Protection' in the installed programs list. Note the version number displayed.Affected if The installed version is 5.2.1 or earlier, or if the version cannot be determined but the product is present.
-
Locate the MyAsUtil ActiveX control componentCheck for the presence of the MyAsUtil ActiveX control by searching for 'MyAsUtil.dll' in the McAfee installation directory (typically C:\Program Files\McAfee\ or C:\Program Files (x86)\McAfee\). Also check the Windows registry under HKEY_CLASSES_ROOT for 'MyAsUtil.InstallInfo' or the associated CLSID.Affected if The MyAsUtil.dll file exists in the McAfee installation folder or the MyAsUtil ActiveX control is registered in the Windows registry.
-
Confirm the vulnerable RunUserProgram method is accessibleVerify the ActiveX control exposes the InstallInfo.RunUserProgram method by checking the registry entry under HKEY_CLASSES_ROOT\MyAsUtil.InstallInfo\ or by examining the DLL's exported functions if accessible. This method is the attack vector for the vulnerability.Affected if The MyAsUtil.InstallInfo interface with the RunUserProgram method is registered and available on the system.
A system is affected if McAfee SaaS Endpoint Protection version 5.2.1 or earlier is installed AND the MyAsUtil ActiveX control (exposing the RunUserProgram function) is present and 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 dataUpdate McAfee SaaS Endpoint Protection to a version newer than 5.2.1, or disable the vulnerable MyAsUtil ActiveX control in affected browsers as a compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3006 — 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-3006 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