Google Chrome up to 2.0.172.32 Password Manager login_prompt.cc Stored credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Google Chrome up to 2.0.172.32. This issue affects some unknown processing of the file browser/login/login_prompt.cc of the component Password Manager. The manipulation leads to credentials management (Stored). This vulnerability is traded as CVE-2010-0556. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Google Chrome up to 2.0.172.32 (Web Browser). This issue affects some unknown processing of the file browser/login/login_prompt.cc of the component Password Manager. The manipulation with an unknown input leads to a credentials management vulnerability (Stored). Using CWE to declare the problem leads to CWE-255. Impacted is integrity. The summary by CVE is:
browser/login/login_prompt.cc in Google Chrome before 4.0.249.89 populates an authentication dialog with credentials that were stored by Password Manager for a different web site, which allows user-assisted remote HTTP servers to obtain sensitive information via a URL that requires authentication, as demonstrated by a URL in the SRC attribute of an IMG element.
The weakness was shared 02/10/2010 by Timothy D. Morgan (SkyLined) (Website). The advisory is shared at googlechromereleases.blogspot.com. The identification of this vulnerability is CVE-2010-0556 since 02/05/2010. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 44587 (Google Chrome < 4.0.249.89 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows. The commercial vulnerability scanner Qualys is able to test this issue with plugin 116891 (Google Chrome Multiple Vulnerabilities(versions prior to 4.0.249.89)).
Upgrading to version 2.0.172.33 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 (44587), SecurityFocus (BID 38177†), OSVDB (62319†), Secunia (SA38545†) and SecurityTracker (ID 1023583†). The entries VDB-51876, VDB-51874, VDB-51873 and VDB-51872 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
- 2.0.172.0
- 2.0.172.1
- 2.0.172.2
- 2.0.172.3
- 2.0.172.4
- 2.0.172.5
- 2.0.172.6
- 2.0.172.7
- 2.0.172.8
- 2.0.172.9
- 2.0.172.10
- 2.0.172.11
- 2.0.172.12
- 2.0.172.13
- 2.0.172.14
- 2.0.172.15
- 2.0.172.16
- 2.0.172.17
- 2.0.172.18
- 2.0.172.19
- 2.0.172.20
- 2.0.172.21
- 2.0.172.22
- 2.0.172.23
- 2.0.172.24
- 2.0.172.25
- 2.0.172.26
- 2.0.172.27
- 2.0.172.28
- 2.0.172.29
- 2.0.172.30
- 2.0.172.31
- 2.0.172.32
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: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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
Name: StoredClass: Credentials management / Stored
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 44587
Nessus Name: Google Chrome < 4.0.249.89 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 902120
OpenVAS Name: Google Chrome Multiple Vulnerabilities - (Windows)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Chrome 2.0.172.33
Timeline
02/05/2010 🔍02/10/2010 🔍
02/10/2010 🔍
02/10/2010 🔍
02/10/2010 🔍
02/11/2010 🔍
02/11/2010 🔍
02/11/2010 🔍
02/16/2010 🔍
02/18/2010 🔍
03/18/2015 🔍
04/30/2026 🔍
Sources
Vendor: google.comProduct: google.com
Advisory: googlechromereleases.blogspot.com
Researcher: Timothy D. Morgan (SkyLined)
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2010-0556 (🔍)
GCVE (CVE): GCVE-0-2010-0556
GCVE (VulDB): GCVE-100-51869
OVAL: 🔍
X-Force: 56216
SecurityFocus: 38177 - Google Chrome prior to 4.0.249.89 Multiple Security Vulnerabilities
Secunia: 38545 - Google Chrome Multiple Vulnerabilities, Highly Critical
OSVDB: 62319 - Google Chrome browser/login/login_prompt.cc HTTP Authentication Dialog Domain Name Unspecified Issue
SecurityTracker: 1023583 - Google Chrome Bugs Let Remote Users Execute Arbitrary Code and Obtain Information
Vulnerability Center: 24860 - Google Chrome Before 4.0.249.89 Remote Multiple Vulnerabilities, High
Vupen: ADV-2010-0361
See also: 🔍
Entry
Created: 03/18/2015 15:15Updated: 04/30/2026 23:51
Changes: 03/18/2015 15:15 (71), 08/24/2017 09:09 (19), 09/02/2021 10:52 (3), 09/02/2021 10:59 (1), 02/01/2025 21:10 (16), 04/30/2026 23:51 (1)
Complete: 🔍
Cache ID: 216::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.