5.0
MEDIUM
CVE-2014-3201
Google Chrome Blink Cross-Site Scripting (XSS) in RenderLayerCompositor
Description

core/rendering/compositing/RenderLayerCompositor.cpp in Blink, as used in Google Chrome before 38.0.2125.102 on Android, does not properly handle a certain IFRAME overflow condition, which allows remote attackers to spoof content via a crafted web site that interferes with the scrollbar.

INFO

Published Date :

Oct. 10, 2014, 1:55 a.m.

Last Modified :

Nov. 7, 2023, 2:20 a.m.

Remotely Exploitable :

Yes !

Impact Score :

2.9

Exploitability Score :

10.0
Public PoC/Exploit Available at Github

CVE-2014-3201 has a 1 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

Affected Products

The following products are affected by CVE-2014-3201 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Google chrome
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2014-3201.

URL Resource
http://googlechromereleases.blogspot.com/2014/10/chrome-for-android-update.html
https://crbug.com/406593
https://src.chromium.org/viewvc/blink?revision=182021&view=revision

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

None

Updated: 7 months, 1 week ago
6 stars 0 fork 0 watcher
Born at : June 23, 2017, 12:07 p.m. This repo has been linked 9 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2014-3201 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2014-3201 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by [email protected]

    May. 14, 2024

    Action Type Old Value New Value
  • CVE Source Update by [email protected]

    Nov. 07, 2023

    Action Type Old Value New Value
    Changed Source Google Inc. Chrome
  • CVE Modified by [email protected]

    Nov. 07, 2023

    Action Type Old Value New Value
    Added Reference Chrome http://googlechromereleases.blogspot.com/2014/10/chrome-for-android-update.html [No types assigned]
    Added Reference Chrome https://src.chromium.org/viewvc/blink?revision=182021&view=revision [No types assigned]
    Added Reference Chrome https://crbug.com/406593 [No types assigned]
    Removed Reference Google Inc. https://crbug.com/406593
    Removed Reference Google Inc. https://src.chromium.org/viewvc/blink?revision=182021&view=revision
    Removed Reference Google Inc. http://googlechromereleases.blogspot.com/2014/10/chrome-for-android-update.html
  • Initial Analysis by [email protected]

    Oct. 10, 2014

    Action Type Old Value New Value
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Exploit Prediction

EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.

0.21 }} 0.01%

score

0.58350

percentile

CVSS2 - Vulnerability Scoring System
Access Vector
Access Complexity
Authentication
Confidentiality
Integrity
Availability