Microsoft Edge prior 122.0.2365.92 on Android information disclosure

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

Summaryinfo

A vulnerability was found in Microsoft Edge on Android. It has been classified as problematic. Impacted is an unknown function. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2024-26246. It is possible to launch the attack on the physical device. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Microsoft Edge on Android. It has been rated as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.

The advisory is shared at msrc.microsoft.com. The identification of this vulnerability is CVE-2024-26246 since 02/15/2024. The exploitation is known to be easy. An attack has to be approached locally. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 122.0.2365.92 eliminates this 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: 3.2
VulDB Meta Temp Score: 3.2

VulDB Base Score: 1.8
VulDB Temp Score: 1.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 3.9
NVD Vector: 🔍

CNA Base Score: 3.9
CNA Vector (Microsoft Corporation): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Yes
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Edge 122.0.2365.92

Timelineinfo

02/15/2024 🔍
03/14/2024 +28 days 🔍
03/15/2024 +0 days 🔍
04/15/2024 +31 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: msrc.microsoft.com
Status: Confirmed

CVE: CVE-2024-26246 (🔍)
GCVE (CVE): GCVE-0-2024-26246
GCVE (VulDB): GCVE-100-256877
scip Labs: https://www.scip.ch/en/?labs.20130704

Entryinfo

Created: 03/15/2024 00:59
Updated: 04/15/2024 15:07
Changes: 03/15/2024 00:59 (49), 04/15/2024 15:07 (25)
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!