Skip to content
Fencer Intel
critical 9.3

CVE-2011-4693 json

Unspecified vulnerability in Adobe Flash Player 11.1.102.55 on Windows and Mac OS X allows remote attackers to execute arbitrary code via a…

published 2011-12-07 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4611

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.1%
EPSS 7.1% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

Unspecified vulnerability in Adobe Flash Player 11.1.102.55 on Windows and Mac OS X allows remote attackers to execute arbitrary code via a crafted SWF file, as demonstrated by the first of two vulnerabilities exploited by the Intevydis vd_adobe_fp module in VulnDisco Step Ahead (SA). NOTE: as of 20111207, this disclosure has no actionable information. However, because the module author is a reliable researcher, the issue is being assigned a CVE identifier for tracking purposes.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-4693 updated cvss 6.8

flash-plugin: arbitrary code execution via unspecified vulnerability

  • Red Hat Enterprise Linux 5 flash-plugin Red Hat Enterprise Linux 6 flash-plugin
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

7.11% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • partners.immunityinc.com http://partners.immunityinc.com/movies/VulnDisco-Flash0day-v2.mov referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.