Intel Cpu 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

81
91
101

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 Fix49
Temporary Fix0
Workaround5
Unavailable0
Not Defined60

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

High0
Functional0
Proof-of-Concept2
Unproven0
Not Defined112

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
Physical7
Local86
Adjacent8
Network13

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
High16
Low89
None9

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
Required1
None113

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
≤38
≤414
≤527
≤639
≤720
≤85
≤91
≤100

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
≤21
≤37
≤414
≤527
≤639
≤721
≤84
≤91
≤100

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
≤23
≤313
≤425
≤513
≤639
≤717
≤84
≤90
≤100

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
≤30
≤41
≤55
≤625
≤718
≤810
≤90
≤100

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
≤41
≤53
≤64
≤74
≤87
≤93
≤100

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
≤31
≤41
≤50
≤61
≤74
≤81
≤90
≤100

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

<1k4
<2k9
<5k37
<10k54
<25k10
<50k0
<100k0
≥100k0

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

<1k70
<2k7
<5k16
<10k17
<25k4
<50k0
<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 (3): 8, 9, 10

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

Software Type: Chip Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
03/14/20245.55.5Intel CPU BIOS Firmware toctou$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2023-32282
03/12/20244.44.4Intel CPU Return Predictor Target information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2023-38575
03/12/20246.56.5Intel CPU Bus Lock Regulator denial of service$5k-$25k$5k-$25kNot DefinedNot Defined0.08CVE-2023-39368
11/14/20236.06.0Intel CPU BIOS Firmware out-of-bounds$5k-$25k$0-$5kNot DefinedNot Defined0.04CVE-2023-25756
11/14/20232.92.9Intel CPU BIOS Firmware denial of service$5k-$25k$0-$5kNot DefinedNot Defined0.04CVE-2023-22329
11/14/20238.18.1Intel CPU unknown vulnerability$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2023-23583
08/11/20234.14.1Intel CPU BIOS Firmware denial of service$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2022-43505
08/11/20236.86.8Intel CPU BIOS Firmware access control$5k-$25k$5k-$25kNot DefinedNot Defined0.04CVE-2022-37343
08/11/20234.14.1Intel CPU BIOS Firmware information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2022-38083
08/11/20233.93.9Intel CPU BIOS Firmware information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2022-27879
08/11/20236.66.6Intel CPU BIOS Firmware input validation$5k-$25k$5k-$25kNot DefinedNot Defined0.04CVE-2022-44611
08/08/20234.54.5Intel CPU Gather Date Sampling Downfall information exposure$5k-$25k$0-$5kNot DefinedNot Defined0.00CVE-2022-40982
05/30/20232.52.5Intel CPU information disclosure$0-$5k$0-$5kNot DefinedWorkaround0.02CVE-2022-28693
05/10/20233.03.0Intel CPU BIOS Firmware information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2022-38087
02/17/20236.96.9Intel CPU BIOS initialization$5k-$25k$0-$5kNot DefinedNot Defined0.00CVE-2022-32231
02/17/20236.86.8Intel CPU TXT SINIT ACM initialization$5k-$25k$0-$5kNot DefinedNot Defined0.03CVE-2022-30704
02/17/20236.96.9Intel CPU BIOS Firmware use after free$5k-$25k$0-$5kNot DefinedNot Defined0.00CVE-2022-30539
02/17/20237.07.0Intel CPU BIOS Firmware input validation$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2022-26837
02/17/20237.27.2Intel CPU BIOS Firmware access control$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2022-26343
02/17/20234.74.7Intel CPU BIOS Firmware access control$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2021-0187
02/17/20234.24.2Intel CPU Software Guard Extension information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-38090
11/12/20227.27.2Intel CPU BIOS Firmware input validation$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2022-26006
11/12/20227.37.3Intel CPU BIOS Firmware toctou$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2022-21198
08/19/20227.07.0Intel CPU BIOS Firmware out-of-bounds write$5k-$25k$5k-$25kNot DefinedNot Defined0.03CVE-2021-33060
08/19/20224.44.4Intel CPU information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2022-26373

89 more entries are not shown

more entries by Intel

Do you want to use VulDB in your project?

Use the official API to access entries easily!