CVE-2014-1748
NoneCVSS
—
EPSS
1.5%
Published
May 21, 2014
CISA due date
—
Cloudanix analysis
An outdated browser version had a flaw that could make parts of a webpage's display extend incorrectly and trick people into seeing or doing the wrong thing.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Low
- Impact
- Data Tampering
- Component
- Application
- Class
- Other
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
The ScrollView::paint function in Blink allows remote attackers to extend scrollbar painting into the parent frame, enabling UI spoofing that alters visual elements without altering underlying content or requiring authentication.
Why it matters to the business
Attackers could trick users into making incorrect decisions based on falsified interface elements in outdated browser versions, leading to potential data exposure or fraudulent actions with minimal operational disruption but elevated phishing risk in legacy environments.
How an attack unfolds
An attacker hosts a malicious webpage that loads content triggering the ScrollView painting flaw in Blink; when rendered in an affected Chrome version, the scrollbar extends across frames to overlay spoofed UI elements that deceive the user into unintended interactions.
How to fix it
Upgrade Google Chrome to version 35.0.1916.114 or later to correct the ScrollView painting behavior; apply browser updates across all instances and enforce automatic update policies to prevent reintroduction of the flaw.
How to confirm the fix worked
Confirm the installed Chrome version is 35.0.1916.114 or newer; test rendering of cross-frame scrollbars in controlled pages to verify painting remains confined to the intended frame.
Typical attack path
- Host a crafted webpage exploiting Blink's ScrollView painting logic
- Deliver the URL to a victim using an affected browser version
- Victim loads the page causing scrollbar to paint into the parent frame
- Spoofed UI elements appear to manipulate user actions or perceptions
How to detect it
Review web server logs and browser telemetry for unusual cross-frame rendering requests; examine historical access logs around 2014-era activity for repeated visits to sites known to test scrollbar behavior, though active exploitation indicators are unlikely given the CVE's age and low EPSS.
What your security team should do
- Prioritize browser inventory scans to identify any remaining instances below the fixed version
- Enforce enterprise update mechanisms and disable legacy browser fallbacks
- Monitor for any user reports of unexpected UI behavior in web applications
The record
The ScrollView::paint function in platform/scroll/ScrollView.cpp in Blink, as used in Google Chrome before 35.0.1916.114, allows remote attackers to spoof the UI by extending scrollbar painting into the parent frame.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:7 | chromium-browser | 0 | 35.0.1916.114-1~deb7u2 |
| Mageia:5 | webkit | 0 | 2.4.10-1.mga5 |
| Ubuntu:14.04:LTS | chromium-browser | 0 | 36.0.1985.125-0ubuntu1.14.04.0~pkg1029 |
| Ubuntu:14.04:LTS | oxide-qt | 0 | 1.0.4-0ubuntu0.14.04.1 |
| Ubuntu:14.04:LTS | webkitgtk | 0 | 2.4.10-0ubuntu0.14.04.1 |
| openSUSE:Tumbleweed | chromium | 0 | 113.0.5672.92-1.1 |
| openSUSE:Tumbleweed | chromium | 0 | 55.0.2883.75-3.1 |
| openSUSE:Tumbleweed | gtk3 | 0 | 2.4.11-3.3 |
Related vulnerabilities
- CVE-2014-3178 Use-after-free vulnerability in core/dom/Node.cpp in Blink, as used in Google Chrome… Also affects chromium-browser
- CVE-2014-3168 Use-after-free vulnerability in the SVG implementation in Blink, as used in Google Chrome… Also affects chromium-browser
- CVE-2014-3165 Use-after-free vulnerability in modules/websockets/WorkerThreadableWebSocketChannel.cpp… Also affects chromium-browser
- CVE-2014-1730 Google V8, as used in Google Chrome before 34.0.1847.131 on Windows and OS X and before… Also affects chromium-browser
- CVE-2013-2842 Use-after-free vulnerability in Google Chrome before 27.0.1453.93 allows remote attackers… Also affects chromium-browser
- CVE-2015-1155 The history implementation in WebKit, as used in Apple Safari before 6.2.6, 7.x before… Also affects webkit
- CVE-2016-9651 A missing check for whether a property of a JS object is private in V8 in Google Chrome… Also affects chromium-browser
- CVE-2018-6065 Integer overflow in computing the required allocation size when instantiating a new… Also affects chromium-browser