CVE-2010-1769 json
WebKit in Apple iTunes before 9.2 on Windows, and Apple iOS before 4 on the iPhone and iPod touch, accesses out-of-bounds memory during the…
published 16y ago modified 4mo ago also EUVD-2010-1789
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.9%
- EPSS 6.9% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
WebKit in Apple iTunes before 9.2 on Windows, and Apple iOS before 4 on the iPhone and iPod touch, accesses out-of-bounds memory during the handling of tables, which allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted HTML document, a different vulnerability than CVE-2010-1387 and CVE-2010-1763.
Is CVE-2010-1769 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.92% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
References
-
lists.apple.com
/archives/security-announce/2010//Jun/msg00002.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2011-01/msg00006.html
vendor-advisory
-
lists.apple.com
/archives/security-announce/2010/Jun/msg00003.html
vendor-advisory
- support.apple.com /kb/HT4220
-
secunia.com
/advisories/43068
third-party-advisory
-
vupen.com
/english/advisories/2011/0212
vdb-entry
- support.apple.com /kb/HT4225
-
secunia.com
/advisories/40196
third-party-advisory
-
vupen.com
/english/advisories/2010/1512
vdb-entry
-
securityfocus.com
/bid/41016
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A7178
vdb-entry, signature
-
securitytracker.com
/id?1024108
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59508
vdb-entry
Sources
- CVE List CVE-2010-1769
- NVD CVE-2010-1769
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.