CVE-2009-1700 json
The XSLT implementation in WebKit in Apple Safari before 4.0, iPhone OS 1.0 through 2.2.1, and iPhone OS for iPod touch 1.1 through 2.2.1 d…
published 2009-06-10 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1695
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
The XSLT implementation in WebKit in Apple Safari before 4.0, iPhone OS 1.0 through 2.2.1, and iPhone OS for iPod touch 1.1 through 2.2.1 does not properly handle redirects, which allows remote attackers to read XML content from arbitrary web pages via a crafted document.
Patch / fix
Exploit prediction
2.62% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/bid/35260 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
lists.apple.com
/archives/security-announce/2009/jun/msg00002.html
vendor-advisory, patch
-
vupen.com
/english/advisories/2009/1522
vdb-entry, patch, vendor-advisory
-
support.apple.com
/kb/HT3613
patch, vendor-advisory
-
securityfocus.com
/bid/35260
vdb-entry, exploit
-
lists.apple.com
/archives/security-announce/2009/Jun/msg00005.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2011-01/msg00006.html
vendor-advisory
-
secunia.com
/advisories/35379
third-party-advisory, vendor-advisory
- support.apple.com /kb/HT3639
-
secunia.com
/advisories/43068
third-party-advisory
-
vupen.com
/english/advisories/2009/1621
vdb-entry
-
vupen.com
/english/advisories/2011/0212
vdb-entry
-
osvdb.org
/54973
vdb-entry
Sources
- CVE List CVE-2009-1700
- NVD CVE-2009-1700
Fencer Vulns 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.