CVE-2010-1386 json
page/Geolocation.cpp in WebCore in WebKit before r56188 and before 1.2.5 does not properly restrict access to the lastPosition function, wh…
published 16y ago modified 4mo ago also EUVD-2010-1414
- cvss
- 10.0
- 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 82%
- public exploits
- 0
- none known
Summary
page/Geolocation.cpp in WebCore in WebKit before r56188 and before 1.2.5 does not properly restrict access to the lastPosition function, which has unspecified impact and remote attack vectors, aka rdar problem 7746357.
Is CVE-2010-1386 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.13% chance of exploitation in the next 30 days, higher than 82% 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 |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
mandriva.com
/security/advisories?name=MDVSA-2011:039
vendor-advisory
-
ubuntu.com
/usn/USN-1006-1
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2011-01/msg00006.html
vendor-advisory
-
vupen.com
/english/advisories/2010/2722
vdb-entry, vendor-advisory
-
secunia.com
/advisories/43068
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/41856
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2011/0212
vdb-entry, vendor-advisory
-
vupen.com
/english/advisories/2011/0552
vdb-entry, vendor-advisory
- security-tracker.debian.org /tracker/CVE-2010-1386
-
securityfocus.com
/bid/42500
vdb-entry
- trac.webkit.org /changeset/56188
- bugs.webkit.org /show_bug.cgi?id=36255
Sources
- CVE List CVE-2010-1386
- NVD CVE-2010-1386
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.