CVE-2015-1300
N/A
Published: September 3, 2015 at 10:00 PM UTC
Updated: June 17, 2026 at 12:22 AM UTC
1 product affected across 1 vendorChrome
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 2%
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.
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (10)
x_refsource_CONFIRM
Source: [email protected]
http://googlechromereleases.blogspot.com/2015/09/stable-channel-update.htmlVendor Advisoryx_refsource_SUSE
Source: [email protected]
http://lists.opensuse.org/opensuse-updates/2015-09/msg00029.htmlVendor Advisoryx_refsource_SUSE
Source: [email protected]
http://lists.opensuse.org/opensuse-updates/2015-11/msg00013.htmlVendor Advisoryx_refsource_REDHAT
Source: [email protected]
http://rhn.redhat.com/errata/RHSA-2015-1712.htmlVendor Advisoryx_refsource_DEBIAN
Source: [email protected]
http://www.debian.org/security/2015/dsa-3351x_refsource_CONFIRM
Source: [email protected]
https://code.google.com/p/chromium/issues/detail?id=511616Quick Info
StatusMODIFIED
CWE
CWE-254
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card