Description
The FrameFetchContext::updateTimingInfoForIFrameNavigation function in core/loader/FrameFetchContext.cpp in Blink, as used in Google Chrome before 45.0.2454.85, does not properly restrict the availability of IFRAME Resource Timing API times, which allows remote attackers to obtain sensitive information via crafted JavaScript code that leverages a history.back call.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
n/a n/a
n/aaffected
References
- http://lists.opensuse.org/opensuse-updates/2015-11/msg00013.html ↗
- http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.html ↗
- http://rhn.redhat.com/errata/RHSA-2015-1712.html ↗
- http://www.securitytracker.com/id/1033472 ↗
- http://lists.opensuse.org/opensuse-updates/2015-09/msg00029.html ↗
- https://github.com/w3c/resource-timing/issues/29 ↗
- https://src.chromium.org/viewvc/blink?revision=199553&view=revision ↗
- http://www.debian.org/security/2015/dsa-3351 ↗
- https://security.gentoo.org/glsa/201603-09 ↗
- https://code.google.com/p/chromium/issues/detail?id=511616 ↗