Google Chrome 0.2.149.29/0.2.149.30 windowopen input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Google Chrome 0.2.149.29/0.2.149.30. Affected is the function windowopen. This manipulation causes input validation.
This vulnerability appears as CVE-2008-4340. In addition, an exploit is available.
Details
A vulnerability classified as problematic was found in Google Chrome 0.2.149.29/0.2.149.30 (Web Browser). Affected by this vulnerability is the function windowopen. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect availability. The summary by CVE is:
Google Chrome 0.2.149.29 and 0.2.149.30 allows remote attackers to cause a denial of service (memory consumption) via an HTML document containing a carriage return ("\r\n\r\n") argument to the window.open function.
The weakness was presented 09/30/2008 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is known as CVE-2008-4340 since 09/30/2008. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
It is possible to download the exploit at securityfocus.com. It is declared as highly functional. We expect the 0-day to have been worth approximately $25k-$100k.
Upgrading eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com.
The vulnerability is also documented in the databases at X-Force (45403), Exploit-DB (6554) and SecurityFocus (BID 31375†). Be aware that VulDB is the high quality source for vulnerability data.
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: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Upgrade: chrome.google.com
Timeline
09/24/2008 🔍09/30/2008 🔍
09/30/2008 🔍
09/30/2008 🔍
03/17/2015 🔍
11/04/2024 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: securityfocus.com⛔
Status: Confirmed
CVE: CVE-2008-4340 (🔍)
GCVE (CVE): GCVE-0-2008-4340
GCVE (VulDB): GCVE-100-44263
X-Force: 45403 - Google Chrome carriage return denial of service
SecurityFocus: 31375 - Google Chrome Carriage Return Remote Denial of Service Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/17/2015 16:11Updated: 11/04/2024 19:18
Changes: 03/17/2015 16:11 (58), 10/09/2018 10:54 (2), 11/04/2024 19:18 (21)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.