CVE-2009-1713 json
The XSLT functionality in WebKit in Apple Safari before 4.0 does not properly implement the document function, which allows remote attacker…
published 2009-06-10 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1708
- cvss
- 7.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
The XSLT functionality in WebKit in Apple Safari before 4.0 does not properly implement the document function, which allows remote attackers to read (1) arbitrary local files and (2) files from different security zones via unspecified vectors.
Patch / fix
Exploit prediction
2.05% chance of exploitation in the next 30 days, higher than 81% 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 | 7.1 | AV:N/AC:M/Au:N/C:C/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
-
support.apple.com
/kb/HT3613
patch, vendor-advisory
-
securityfocus.com
/bid/35260
vdb-entry, exploit
-
lists.opensuse.org
/opensuse-security-announce/2011-01/msg00006.html
vendor-advisory
-
ubuntu.com
/usn/USN-857-1
vendor-advisory
-
vupen.com
/english/advisories/2009/1522
vdb-entry, vendor-advisory
-
secunia.com
/advisories/35379
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/43068
third-party-advisory
-
vupen.com
/english/advisories/2011/0212
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/51267
vdb-entry
-
osvdb.org
/54975
vdb-entry
Sources
- CVE List CVE-2009-1713
- NVD CVE-2009-1713
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.