CVE-2010-1728 json
Opera before 10.53 on Windows and Mac OS X does not properly handle a series of document modifications that occur asynchronously, which all…
published 16y ago modified 4mo ago also EUVD-2010-1748
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.0%
- EPSS 7.0% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
Opera before 10.53 on Windows and Mac OS X does not properly handle a series of document modifications that occur asynchronously, which allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via JavaScript that writes <marquee> sequences in an infinite loop, leading to attempted use of uninitialized memory. NOTE: this might overlap CVE-2006-6955.
Is CVE-2010-1728 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
6.98% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- h.ackack.net http://h.ackack.net/?p=258 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 |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
h.ackack.net
/?p=258
exploit
-
opera.com
/support/kb/view/953/
vendor-advisory
-
vupen.com
/english/advisories/2010/0999
vdb-entry, vendor-advisory
-
secunia.com
/advisories/39590
third-party-advisory, vendor-advisory
- opera.com /docs/changelogs/mac/1053/
- opera.com /docs/changelogs/windows/1053/
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11927
vdb-entry, signature
-
exchange.xforce.ibmcloud.com
/vulnerabilities/58231
vdb-entry
- my.opera.com /desktopteam/blog/2010/04/28/opera-10-53-rc1-for-windows-and-mac
Sources
- CVE List CVE-2010-1728
- NVD CVE-2010-1728
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.