Google Chrome up to 53.0.2785 IPC Message render_frame_host_impl.cc null pointer dereference

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.
8.6$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Google Chrome up to 53.0.2785. Affected is an unknown function of the file render_frame_host_impl.cc of the component IPC Message Handler. Performing a manipulation results in null pointer dereference. This vulnerability is reported as CVE-2016-7549. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Chrome up to 53.0.2785 (Web Browser). It has been classified as critical. This affects some unknown functionality of the file render_frame_host_impl.cc of the component IPC Message Handler. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Google Chrome before 53.0.2785.113 does not ensure that the recipient of a certain IPC message is a valid RenderFrame or RenderWidget, which allows remote attackers to cause a denial of service (invalid pointer dereference and application crash) or possibly have unspecified other impact by leveraging access to a renderer process, related to render_frame_host_impl.cc and render_widget_host_impl.cc, as demonstrated by a Password Manager message.

The weakness was disclosed 09/25/2016 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2016-7549 since 09/09/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 93938 (Ubuntu 14.04 LTS / 16.04 LTS : oxide-qt vulnerabilities (USN-3091-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Ubuntu Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 196594 (Ubuntu Security Notification for Oxide-qt Vulnerabilities (USN-3091-1)).

Upgrading to version 53.0.2785.113 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (93938) and SecurityFocus (BID 93160†). The entry VDB-92513 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.6

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
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: 93938
Nessus Name: Ubuntu 14.04 LTS / 16.04 LTS : oxide-qt vulnerabilities (USN-3091-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 862149
OpenVAS Name: Google Chrome Security Updates(stable-channel-update-for-desktop_13-2016-09)-Windows
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Upgrade: Chrome 53.0.2785.113

Timelineinfo

09/09/2016 🔍
09/25/2016 +16 days 🔍
09/25/2016 +0 days 🔍
09/25/2016 +0 days 🔍
09/26/2016 +1 days 🔍
10/07/2016 +11 days 🔍
10/10/2016 +3 days 🔍
09/21/2022 +2172 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: RHSA-2016:1905⛔
Status: Not defined
Confirmation: 🔍

CVE: CVE-2016-7549 (🔍)
GCVE (CVE): GCVE-0-2016-7549
GCVE (VulDB): GCVE-100-92157
SecurityFocus: 93160 - Google Chrome CVE-2016-7549 Multiple Denial of Service Vulnerabilities

See also: 🔍

Entryinfo

Created: 09/26/2016 12:15
Updated: 09/21/2022 11:02
Changes: 09/26/2016 12:15 (70), 04/26/2019 12:08 (13), 09/21/2022 11:02 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!