Google Chrome 29.0.1547.76 204 No Content Status Code authentication spoofing

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Google Chrome 29.0.1547.76. Impacted is an unknown function of the component 204 No Content Status Code Handler. This manipulation causes authentication spoofing. This vulnerability appears as CVE-2013-2916. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Google Chrome 29.0.1547.76 (Web Browser) and classified as problematic. Affected by this vulnerability is an unknown functionality of the component 204 No Content Status Code Handler. The manipulation with an unknown input leads to a authentication spoofing vulnerability. The CWE definition for the vulnerability is CWE-290. This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:

Blink, as used in Google Chrome before 30.0.1599.66, allows remote attackers to spoof the address bar via vectors involving a response with a 204 (aka No Content) status code, in conjunction with a delay in notifying the user of an attempted spoof.

The weakness was presented 10/01/2013 by Masato Kinugawa as 281256 (Website). It is possible to read the advisory at code.google.com. The public release was coordinated in cooperation with Google. This vulnerability is known as CVE-2013-2916 since 04/11/2013. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 70636 (Debian DSA-2785-1 : chromium-browser - several vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 166720 (OpenSuSE Security Update for chromium (openSUSE-SU-2014:0065-1)).

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

The vulnerability is also documented in the databases at Tenable (70636), SecurityFocus (BID 62752†), OSVDB (97976†), Secunia (SA55087†) and Vulnerability Center (SBV-41718†). Additional details are provided at googlechromereleases.blogspot.com. See VDB-9992, VDB-10161, VDB-10162 and VDB-10163 for similar entries. Be aware that VulDB is the high quality source 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: 4.8
VulDB Meta Temp Score: 4.6

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Authentication spoofing
CWE: CWE-290 / CWE-287
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: 70636
Nessus Name: Debian DSA-2785-1 : chromium-browser - several vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 892794
OpenVAS Name: Debian Security Advisory DSA 2785-1 (chromium-browser - several vulnerabilities
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 30.0.1599.66

Timelineinfo

04/11/2013 🔍
10/01/2013 +173 days 🔍
10/01/2013 +0 days 🔍
10/01/2013 +0 days 🔍
10/02/2013 +1 days 🔍
10/02/2013 +0 days 🔍
10/03/2013 +1 days 🔍
05/26/2021 +2792 days 🔍

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: 281256
Researcher: Masato Kinugawa
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-2916 (🔍)
GCVE (CVE): GCVE-0-2013-2916
GCVE (VulDB): GCVE-100-10543

OVAL: 🔍
IAVM: 🔍

SecurityFocus: 62752
Secunia: 55087 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 97976
Vulnerability Center: 41718 - Google Chrome Before 30.0.1599.66 Remote Address Bar Spoofing Vulnerability Related to \x27204 No Content\x27 Status Code - CVE-2013-2916, Medium

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 10/03/2013 13:08
Updated: 05/26/2021 08:08
Changes: 10/03/2013 13:08 (51), 05/12/2017 10:46 (34), 05/26/2021 08:08 (3)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!