CVE-2011-0778 json
Google Chrome before 9.0.597.84 does not properly restrict drag and drop operations, which might allow remote attackers to bypass the Same…
published 2011-02-04 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0790
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
Google Chrome before 9.0.597.84 does not properly restrict drag and drop operations, which might allow remote attackers to bypass the Same Origin Policy via unspecified vectors.
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-0778 updated cvss 3.7
WebKit: restrict cross-origin drag+drop in WebKit
-
Red Hat Enterprise Linux 6 webkitgtkaffected: 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
1.40% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
- Technology feeds
References
-
lists.opensuse.org
/opensuse-security-announce/2011-05/msg00005.html
vendor-advisory
-
debian.org
/security/2011/dsa-2166
vendor-advisory
-
debian.org
/security/2011/dsa-2188
vendor-advisory
-
googlechromereleases.blogspot.com
/2011/02/stable-channel-update.html
vendor-advisory
-
secunia.com
/advisories/43368
third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14228
vdb-entry, signature
-
vupen.com
/english/advisories/2011/0408
vdb-entry
- code.google.com /p/chromium/issues/detail?id=59081
Sources
- CVE List CVE-2011-0778
- NVD CVE-2011-0778
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.