Microsoft Internet Explorer 6/7 Certificate improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Microsoft Internet Explorer 6/7. It has been classified as critical. This issue affects some unknown processing of the component Certificate Handler. This manipulation causes improper authentication. This vulnerability appears as CVE-2009-2069. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability has been found in Microsoft Internet Explorer 6/7 (Web Browser) and classified as critical. Affected by this vulnerability is an unknown code block of the component Certificate Handler. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:
Microsoft Internet Explorer before 8 displays a cached certificate for a (1) 4xx or (2) 5xx CONNECT response page returned by a proxy server, which allows man-in-the-middle attackers to spoof an arbitrary https site by letting a browser obtain a valid certificate from this site during one request, and then sending the browser a crafted 502 response page upon a subsequent request.
The weakness was presented 06/15/2009. This vulnerability is known as CVE-2009-2069. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version bis 7 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (51616), SecurityFocus (BID 35411†) and Vulnerability Center (SBV-37812†). See VDB-48616, VDB-48615 and VDB-48614 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Support
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
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: Improper authenticationCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Internet Explorer bis 7
Timeline
05/01/2009 🔍06/15/2009 🔍
06/15/2009 🔍
12/25/2012 🔍
03/17/2015 🔍
08/11/2021 🔍
Sources
Vendor: microsoft.comStatus: Not defined
CVE: CVE-2009-2069 (🔍)
GCVE (CVE): GCVE-0-2009-2069
GCVE (VulDB): GCVE-100-48613
X-Force: 51616
SecurityFocus: 35411
Vulnerability Center: 37812 - Microsoft Internet Explorer \x3C8 and Google Chrome \x3C1.0.154.53 Allows Remote MITM HTTPS Sites Spoofing, Medium
See also: 🔍
Entry
Created: 03/17/2015 23:38Updated: 08/11/2021 18:08
Changes: 03/17/2015 23:38 (40), 04/07/2017 12:09 (11), 08/11/2021 18:08 (8)
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.