Google Chrome OS up to 25.0.1364.126 Service h264_parser.cc ParseSPSScalingLists memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as critical has been found in Google Chrome OS up to 25.0.1364.126. This affects the function 'H264Parser::ParsePPSScalingLists/H264Parser::ParseSPSScalingLists of the file content/common/gpu/media/h264_parser.cc of the component Service. The manipulation leads to memory corruption.
This vulnerability is documented as CVE-2013-0915. There is not any exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as very critical, has been found in Google Chrome OS up to 25.0.1364.126 (Web Browser). This issue affects the function 'H264Parser::ParsePPSScalingLists/H264Parser::ParseSPSScalingLists of the file content/common/gpu/media/h264_parser.cc of the component Service. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The GPU process in Google Chrome OS before 25.0.1364.173 allows attackers to cause a denial of service or possibly have unspecified other impact via vectors related to an "overflow."
The weakness was released 03/13/2013 by PinkiePie aka PwniePie as 2013/03 as confirmed changelog entry (Website). The advisory is shared at googlechromereleases.blogspot.ch. The public release was coordinated with Google. The identification of this vulnerability is CVE-2013-0915 since 01/07/2013. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 05/14/2017). It is expected to see the exploit prices for this product increasing in the near future.
Upgrading to version 25.0.1364.173 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at chromiumcodereview.appspot.com. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (82854), SecurityFocus (BID 58521†), OSVDB (91426†), SecurityTracker (ID 1028320†) and Vulnerability Center (SBV-42087†). Entries connected to this vulnerability are available at VDB-7941 and VDB-7994. 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/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Chrome OS 25.0.1364.173
Patch: chromiumcodereview.appspot.com
Timeline
01/07/2013 🔍03/13/2013 🔍
03/13/2013 🔍
03/15/2013 🔍
03/18/2013 🔍
03/19/2013 🔍
03/19/2013 🔍
10/24/2013 🔍
05/14/2017 🔍
Sources
Vendor: google.comAdvisory: 2013/03
Researcher: PinkiePie aka PwniePie
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍
CVE: CVE-2013-0915 (🔍)
GCVE (CVE): GCVE-0-2013-0915
GCVE (VulDB): GCVE-100-8021
X-Force: 82854
SecurityFocus: 58521
OSVDB: 91426
SecurityTracker: 1028320 - Google Chrome Bugs Let Remote Users Execute Arbitrary Code
Vulnerability Center: 42087 - Google Chrome before 25.0.1364.173 Remote Code Execution Vulnerability due to Buffer Overflow GPU Process, Critical
See also: 🔍
Entry
Created: 03/19/2013 12:39Updated: 05/14/2017 09:38
Changes: 03/19/2013 12:39 (53), 05/14/2017 09:38 (21)
Complete: 🔍
Committer:
Cache ID: 216:D84: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.