Google WebkitGTK+ up to 2.0.1 Web Audio pull memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Google WebkitGTK+ up to 2.0.1. This issue affects the function WebCore::AudioNodeOutput::pull of the component Web Audio. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2013-2845. There is not any exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Google WebkitGTK+ up to 2.0.1 (Web Browser). This affects the function WebCore::AudioNodeOutput::pull of the component Web Audio. 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 summary by CVE is:

The Web Audio implementation in Google Chrome before 27.0.1453.93 allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.

The weakness was released 05/08/2013 by Xingnan Wang with Intel as not defined changelog entry (Website). The advisory is shared at trac.webkit.org. The public release was coordinated with Google. This vulnerability is uniquely identified as CVE-2013-2845 since 04/11/2013. 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 are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/10/2021).

The vulnerability scanner Nessus provides a plugin with the ID 66676 (Debian DSA-2695-1 : chromium-browser - several issues), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 121201 (Google Chrome Prior to 27.0.1453.93 Multiple Vulnerabilities).

Upgrading to version 27.0.1453.93 eliminates this vulnerability. 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 databases at Tenable (66676), SecurityFocus (BID 60063†), OSVDB (93249†) and Secunia (SA53430†). Entries connected to this vulnerability are available at VDB-8503, VDB-8559, VDB-8840 and VDB-8841. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 66676
Nessus Name: Debian DSA-2695-1 : chromium-browser - several issues
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 892695
OpenVAS Name: Debian Security Advisory DSA 2695-1 (chromium-browser - several issues
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: WebkitGTK+ 27.0.1453.93
Patch: trac.webkit.org

Timelineinfo

04/11/2013 🔍
05/08/2013 +27 days 🔍
05/08/2013 +0 days 🔍
05/14/2013 +6 days 🔍
05/21/2013 +6 days 🔍
05/22/2013 +1 days 🔍
05/22/2013 +0 days 🔍
05/30/2013 +8 days 🔍
05/10/2021 +2902 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: trac.webkit.org
Researcher: Xingnan Wang
Organization: Intel
Status: Not defined
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-2845 (🔍)
GCVE (CVE): GCVE-0-2013-2845
GCVE (VulDB): GCVE-100-8661

OVAL: 🔍

SecurityFocus: 60063
Secunia: 53430 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 93249

See also: 🔍

Entryinfo

Created: 05/14/2013 16:18
Updated: 05/10/2021 17:22
Changes: 05/14/2013 16:18 (78), 03/20/2019 20:04 (1), 05/10/2021 17:22 (3)
Complete: 🔍
Committer:
Cache ID: 216:CAC:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!