Microsoft Edge Crash Reporting stack-based overflow
|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.
A vulnerability classified as critical has been found in Microsoft Edge (Web Browser) (version unknown). Affected is an unknown part of the component Crash Reporting. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability.
The weakness was disclosed 03/13/2023 as confirmed security guidance (Website). The advisory is available at portal.msrc.microsoft.com. This vulnerability is traded as CVE-2023-1217. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 03/14/2023).
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
CVSSv3VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Stack-based overflow
CWE: CWE-121 / CWE-119
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline03/13/2023 Advisory disclosed
03/13/2023 +0 days Countermeasure disclosed
03/14/2023 +0 days VulDB entry created
03/14/2023 +0 days VulDB last update
CVE: CVE-2023-1217 (🔒)
EntryCreated: 03/14/2023 08:14 PM
Updated: 03/14/2023 08:18 PM
Changes: 03/14/2023 08:14 PM (12), 03/14/2023 08:18 PM (31)
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!
No comments yet. Languages: en.
Please log in to comment.