| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Google Chrome up to 8.0.552.208. The impacted element is an unknown function of the component Libraries. Performing a manipulation results in denial of service. This vulnerability is cataloged as CVE-2011-0782. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Google Chrome up to 8.0.552.208 (Web Browser). This affects some unknown processing of the component Libraries. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:
Google Chrome before 9.0.597.84 on Mac OS X does not properly mitigate an unspecified flaw in the Mac OS X 10.5 SSL libraries, which allows remote attackers to cause a denial of service (application crash) via unknown vectors.
The weakness was shared 02/04/2011 (Website). The advisory is shared at googlechromereleases.blogspot.com. This vulnerability is uniquely identified as CVE-2011-0782. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 118954 (Google Chrome Prior to 9.0.597.84 Multiple Vulnerabilities).
Upgrading to version 8.0.552.209 eliminates this vulnerability. The upgrade is hosted for download at chrome.google.com.
The vulnerability is also documented in the vulnerability database at Vulnerability Center (SBV-29563†). The entries VDB-4281, VDB-56351, VDB-56350 and VDB-56348 are related to this item. 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/
- 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: Denial of serviceCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Chrome 8.0.552.209
Timeline
02/04/2011 🔍02/04/2011 🔍
02/04/2011 🔍
02/04/2011 🔍
02/06/2011 🔍
03/20/2015 🔍
10/13/2021 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: googlechromereleases.blogspot.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2011-0782 (🔍)
GCVE (CVE): GCVE-0-2011-0782
GCVE (VulDB): GCVE-100-56349
OVAL: 🔍
Vulnerability Center: 29563 - Google Chrome before 9.0.597.84 on Mac OS X Remote DoS via Unknown Vectors, Medium
See also: 🔍
Entry
Created: 03/20/2015 16:16Updated: 10/13/2021 19:24
Changes: 03/20/2015 16:16 (54), 03/14/2017 12:02 (6), 10/13/2021 19:24 (4)
Complete: 🔍
Cache ID: 216:881: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.