Microsoft Edge Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

99.0.1150.3020
98.0.1108.4317
102.0.1245.414
104.0.1293.473
103.0.1264.373

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix840
Temporary Fix0
Workaround2
Unavailable1
Not Defined1

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High2
Functional1
Proof-of-Concept146
Unproven23
Not Defined672

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical1
Local4
Adjacent2
Network837

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High15
Low10
None819

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required779
None65

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤31
≤423
≤5103
≤6402
≤7160
≤8144
≤99
≤102

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤312
≤417
≤5112
≤6498
≤7107
≤887
≤910
≤101

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤33
≤417
≤5106
≤635
≤7571
≤8101
≤99
≤102

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤31
≤415
≤587
≤629
≤754
≤8446
≤954
≤103

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤31
≤40
≤55
≤62
≤74
≤85
≤916
≤101

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤32
≤424
≤5431
≤610
≤748
≤822
≤911
≤102

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k0
<2k0
<5k1
<10k1
<25k3
<50k156
<100k633
≥100k50

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k110
<2k33
<5k99
<10k192
<25k407
<50k3
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (10): 11.0.10240.16384, 38.14393, 38.14393.1066, 98.0.1108.43, 99.0.1150.3, 102.0.1245.39, 102.0.1245.41, 103.0.1264.37, 103.0.1264.44, 104.0.1293.47

Link to Product Website: https://www.microsoft.com/

Software Type: Web Browser

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
11/28/20226.36.0Microsoft Edge GPU heap-based overflow$25k-$100k$5k-$25kHighOfficial Fix4.62CVE-2022-4135
10/11/202210.08.7Microsoft Azure Stack Edge privileges management$100k and more$25k-$100kUnprovenOfficial Fix0.03CVE-2022-37968
10/06/20227.57.4Microsoft Edge V8 out-of-bounds write$25k-$100k$5k-$25kNot DefinedOfficial Fix0.03CVE-2022-3373
10/06/20227.57.4Microsoft Edge Custom Elements use after free$25k-$100k$5k-$25kNot DefinedOfficial Fix0.04CVE-2022-3370
10/03/20227.57.4Microsoft Edge Media use after free$25k-$100k$5k-$25kNot DefinedOfficial Fix0.05CVE-2022-3307
10/03/20226.86.7Microsoft Edge Developer Tools Remote Code Execution$25k-$100k$5k-$25kNot DefinedOfficial Fix0.08CVE-2022-3308
10/03/20227.26.9Microsoft Edge race condition$25k-$100k$5k-$25kProof-of-ConceptOfficial Fix0.03CVE-2022-41035
10/03/20227.57.4Microsoft Edge CSS use after free$25k-$100k$5k-$25kNot DefinedOfficial Fix0.00CVE-2022-3304
10/03/20226.46.2Microsoft Edge Custom Tabs Remote Code Execution$25k-$100k$5k-$25kNot DefinedOfficial Fix0.03CVE-2022-3310
10/03/20225.35.2Microsoft Edge Safe Browsing input validation$25k-$100k$5k-$25kNot DefinedOfficial Fix0.03CVE-2022-3316
10/03/20227.57.4Microsoft Edge Blink type confusion$25k-$100k$5k-$25kNot DefinedOfficial Fix0.03CVE-2022-3315
10/03/20226.46.2Microsoft Edge Full Screen Remote Code Execution$25k-$100k$5k-$25kNot DefinedOfficial Fix0.05CVE-2022-3313
10/03/20226.46.2Microsoft Edge Import use after free$25k-$100k$5k-$25kNot DefinedOfficial Fix0.75CVE-2022-3311
09/01/20227.56.9Microsoft Edge Remote Code Execution$25k-$100k$5k-$25kUnprovenOfficial Fix0.04CVE-2022-38012
08/05/20227.16.5Microsoft Edge race condition$25k-$100k$5k-$25kUnprovenOfficial Fix0.03CVE-2022-35796
08/05/20228.68.1Microsoft Edge Remote Code Execution$25k-$100k$5k-$25kUnprovenOfficial Fix0.03CVE-2022-33649
08/05/20227.97.2Microsoft Edge race condition$25k-$100k$5k-$25kUnprovenOfficial Fix0.00CVE-2022-33636
07/06/20226.36.0Microsoft Edge V8 type confusion$25k-$100k$5k-$25kNot DefinedOfficial Fix0.04CVE-2022-2295
07/06/20226.36.0Microsoft Edge WebRTC heap-based overflow$25k-$100k$5k-$25kNot DefinedOfficial Fix0.11CVE-2022-2294
06/30/20227.97.2Microsoft Edge privileges management$25k-$100k$5k-$25kUnprovenOfficial Fix0.03CVE-2022-33680
06/24/20227.77.2Microsoft Edge Remote Code Execution$25k-$100k$5k-$25kUnprovenOfficial Fix0.05CVE-2022-33639
06/23/20227.97.2Microsoft Edge Remote Code Execution$25k-$100k$5k-$25kUnprovenOfficial Fix0.00CVE-2022-33638
06/23/20227.97.2Microsoft Edge Remote Code Execution$25k-$100k$5k-$25kUnprovenOfficial Fix0.04CVE-2022-30192
06/13/20226.36.0Microsoft Edge ANGLE use after free$25k-$100k$5k-$25kNot DefinedOfficial Fix0.05CVE-2022-2011
06/13/20226.36.0Microsoft Edge Compositing out-of-bounds$25k-$100k$5k-$25kNot DefinedOfficial Fix0.03CVE-2022-2010

819 more entries are not shown

more entries by Microsoft

Interested in the pricing of exploits?

See the underground prices here!