Google Chrome up to 25.0.1364.160 ImageLoader Object ImageInputType memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Chrome up to 25.0.1364.160. This vulnerability affects the function ImageInputType of the component ImageLoader Object. Performing a manipulation results in memory corruption.
Furthermore, there is an exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Google Chrome up to 25.0.1364.160 (Web Browser). It has been classified as critical. This affects the function ImageInputType of the component ImageLoader Object. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was shared 03/11/2013 by Darin Adler as 145423 as not defined changelog entry (Website). The advisory is shared at trac.webkit.org. The vendor cooperated in the coordination of the public release. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
After immediately, there has been an exploit disclosed. The exploit is shared for download at trac.webkit.org. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $100k and more.
Upgrading eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at trac.webkit.org. The best possible mitigation is suggested to be patching the affected component. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (91207†). The entry VDB-7991 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
- Product: https://www.google.com/chrome/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.0
VulDB Base Score: 10.0
VulDB Temp Score: 9.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍
Upgrade: chrome.google.com
Patch: trac.webkit.org
Timeline
03/11/2013 🔍03/11/2013 🔍
03/11/2013 🔍
03/15/2013 🔍
05/04/2018 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: 145423
Researcher: Darin Adler
Status: Not defined
Coordinated: 🔍
GCVE (VulDB): GCVE-100-7989
OSVDB: 91207
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/15/2013 10:41Updated: 05/04/2018 09:09
Changes: 03/15/2013 10:41 (52), 05/04/2018 09:09 (2)
Complete: 🔍
Committer:
Cache ID: 216:D16:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.