CVE-2010-2660 json
Opera before 10.54 on Windows and Mac OS X, and before 10.60 on UNIX platforms, does not properly restrict certain uses of homograph charac…
published 16y ago modified 4mo ago also EUVD-2010-2664
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Opera before 10.54 on Windows and Mac OS X, and before 10.60 on UNIX platforms, does not properly restrict certain uses of homograph characters in domain names, which makes it easier for remote attackers to spoof IDN domains via unspecified choices of characters.
Patch / fix
- vupen.com/english/advisories/2010/1673 advisory
- vupen.com/english/advisories/2010/1529 advisory
Is CVE-2010-2660 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
2.27% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
vupen.com
/english/advisories/2010/1673
vdb-entry, patch, vendor-advisory
-
vupen.com
/english/advisories/2010/1529
vdb-entry, patch, vendor-advisory
-
secunia.com
/advisories/40250
third-party-advisory, vendor-advisory
-
opera.com
/support/search/view/961/
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11603
vdb-entry, signature
-
securityfocus.com
/bid/40973
vdb-entry
- opera.com /docs/changelogs/unix/1060/
- opera.com /docs/changelogs/mac/1054/
- opera.com /docs/changelogs/windows/1054/
Sources
- CVE List CVE-2010-2660
- NVD CVE-2010-2660
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.