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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Microsoft Edge. Impacted is an unknown function. The manipulation leads to an unknown weakness. This vulnerability is documented as CVE-2021-42308. The attack can be initiated remotely. There is not any exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Microsoft Edge (Web Browser) (affected version unknown). It has been rated as problematic. Using CWE to declare the problem leads to CWE-290. This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. Impacted is integrity.

The weakness was released 11/19/2021 as confirmed security guidance (Website). The advisory is shared at portal.msrc.microsoft.com. The identification of this vulnerability is CVE-2021-42308. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

It is declared as proof-of-concept.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.2
VulDB Meta Temp Score: 4.0

VulDB Base Score: 3.1
VulDB Temp Score: 2.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 3.1
Vendor Vector (Microsoft): 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CNA Base Score: 3.1
CNA Vector (Microsoft): 🔍

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: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

10/12/2021 🔍
11/19/2021 +38 days 🔍
11/19/2021 +0 days 🔍
11/24/2021 +4 days 🔍
08/21/2026 +1731 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: portal.msrc.microsoft.com
Status: Confirmed

CVE: CVE-2021-42308 (🔍)
GCVE (CVE): GCVE-0-2021-42308
GCVE (VulDB): GCVE-100-187181

Entryinfo

Created: 11/24/2021 08:08
Updated: 08/21/2026 15:39
Changes: 11/24/2021 08:08 (26), 11/24/2021 08:09 (8), 11/24/2021 08:12 (19), 11/27/2021 11:28 (2), 08/21/2026 15:39 (44)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!