CVE-2011-0611
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 · uneditedAdobe Flash Player before 10.2.154.27 on Windows, Mac OS X, Linux, and Solaris and 10.2.156.12 and earlier on Android; Adobe AIR before 2.6.19140; and Authplay.dll (aka AuthPlayLib.bundle) in Adobe Reader 9.x before 9.4.4 and 10.x through 10.0.1 on Windows, Adobe Reader 9.x before 9.4.4 and 10.x before 10.0.3 on Mac OS X, and Adobe Acrobat 9.x before 9.4.4 and 10.x before 10.0.3 on Windows and Mac OS X allow remote attackers to execute arbitrary code or cause a denial of service (application crash) via crafted Flash content; as demonstrated by a Microsoft Office document with an embedded .swf file that has a size inconsistency in a "group of included constants," object type confusion, ActionScript that adds custom functions to prototypes, and Date objects; and as exploited in the wild in April 2011.
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 confidenceThis is a critical vulnerability in Adobe Flash Player, Adobe AIR, and Adobe Reader/Acrobat's Authplay.dll component. The flaw allows remote code execution through malicious Flash content (.swf files) embedded in Microsoft Office documents. Exploitation involves object type confusion, manipulation of ActionScript prototypes, and Date objects, taking advantage of a size inconsistency in included constants.
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< 10.0.648.205< 10.2.154.27<= 10.2.156.12>= 9.0, < 9.4.4>= 10.0, <= 10.0.1>= 10.0, < 10.0.3< 2.6.19140>= 9.0, < 9.4>= 10.0, < 10.0.3= 11.2= 11.3= 11.4= 10= 11CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 Adobe Flash Player version in browsersOpen a browser and navigate to 'about:plugin' in Chrome, or visit the Adobe version check page at https://www.adobe.com/software/flash/about/. On Windows, also check C:\Windows\System32\Macromed\Flash\ for the NPSWF32.dll or Flash*.ocx file properties.Affected if The installed Flash Player version is less than 10.2.154.27, or is between 10.2.154.28 and 10.2.156.12 inclusive
-
Check Adobe Acrobat versionOpen Adobe Acrobat, go to Help > About Adobe Acrobat (or press Ctrl+Alt+A). Alternatively, right-click the AcroRd32.exe or AcroTray.exe file in the installation directory and select Properties > Details to view the version.Affected if The Adobe Acrobat version is 9.0 through 9.3.x (less than 9.4), or 10.0 through 10.0.2 (less than 10.0.3)
-
Check Adobe Reader versionOpen Adobe Reader, go to Help > About Adobe Reader. On Windows, also check the version by right-clicking the AdoRd32.exe file in the installation folder and viewing Properties > Details.Affected if The Adobe Reader version is 9.0 through 9.4.3 (less than 9.4.4), or 10.0.0 through 10.0.2 (less than 10.0.3)
-
Check Adobe AIR versionOpen the Windows Control Panel > Programs and Features (or Add/Remove Programs), find Adobe AIR in the list and view the version. On Mac, check /Library/Application Support/Adobe AIR/ for the Adobe AIR Application Installer.app.Affected if The Adobe AIR version is less than 2.6.19140
-
Check Google Chrome bundled Flash versionIn Chrome, type 'chrome://plugins' in the address bar and find the Flash entry, or type 'chrome://version' to see the full version string. The internal Flash component is included with Chrome.Affected if The Chrome version is less than 10.0.648.205 (which includes Flash below the fixed version)
The environment is affected if any installed Adobe Flash Player, Adobe Reader, Adobe Acrobat, Adobe AIR, or Google Chrome version falls within the affected version ranges, and the system processes Flash content (AuthPlayLib component is loaded).
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.
dbcve · scoped2.6.191409.49.4.4
Immediately update Adobe Flash Player to 10.2.154.27+, Adobe AIR to 2.6.19140+, and Adobe Reader/Acrobat to 9.4.4+ or 10.0.3+ as appropriate. Until patches are applied, block Office documents with embedded Flash content at the email gateway or proxy.
Adobe Flash Player 10.2.154.27+ / 10.2.156.12+ (Android); Adobe AIR 2.6.19140+; Adobe Reader/Acrobat 9.4.4+ / 10.0.3+; Chrome 10.0.648.205+
- Identify all installed Adobe products affected by this vulnerability (Flash Player, Adobe AIR, Adobe Reader/Acrobat)
- For Chrome users: Upgrade Chrome to version 10.0.648.205 or later
- For Flash Player users: Upgrade to version 10.2.154.27 or later (10.2.156.12+ for Android)
- For Adobe AIR users: Upgrade to version 2.6.19140 or later
- For Adobe Reader 9.x users: Upgrade to version 9.4.4 or later
- For Adobe Reader 10.x users: Upgrade to version 10.0.3 or later
- For Adobe Acrobat 9.x users: Upgrade to version 9.4.4 or later
- For Adobe Acrobat 10.x users: Upgrade to version 10.0.3 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0611 — 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- lists.opensuse.org
- bugix-security.blogspot.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- www.adobe.com
- www.adobe.com
- www.adobe.com
- www.redhat.com
- www.vupen.com
- www.vupen.com
- www.vupen.com
- lists.opensuse.org
- securityreason.com
- securityreason.com
- www.exploit-db.com
- www.kb.cert.org
- www.securityfocus.com
- www.securitytracker.com
- www.securitytracker.com
- exchange.xforce.ibmcloud.com
- googlechromereleases.blogspot.com
- bugix-security.blogspot.com
- contagiodump.blogspot.com
- blogs.technet.com
- oval.cisecurity.org
- www.cisa.gov
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-0611 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