Amd 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.

Type

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product

AMD EPYC73
AMD CPU50
AMD Ryzen32
AMD Graphics Driver17
AMD Athlon9

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix59
Temporary Fix0
Workaround3
Unavailable1
Not Defined143

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-Concept0
Unproven0
Not Defined206

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
Physical8
Local20
Adjacent135
Network43

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
High6
Low176
None24

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
Required4
None202

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.

CVSSv3 Base

≤10
≤21
≤38
≤414
≤536
≤653
≤750
≤831
≤97
≤106

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
≤38
≤415
≤535
≤655
≤748
≤832
≤96
≤106

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
≤22
≤312
≤431
≤524
≤684
≤730
≤812
≤910
≤101

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
≤40
≤57
≤635
≤711
≤851
≤918
≤1013

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
≤30
≤40
≤50
≤61
≤70
≤80
≤90
≤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
≤30
≤40
≤50
≤60
≤70
≤80
≤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

<1k76
<2k77
<5k51
<10k0
<25k1
<50k0
<100k0
≥100k1

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

<1k171
<2k24
<5k9
<10k0
<25k1
<50k0
<100k1
≥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.

🔴 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 Products (34): 16h Model 00h Processor (1), ATI (1), ATIDXX64.DLL (4), ATI Diagnostics Hardware Abstraction Sys Overclocking Utility (1), ATIKMDAG.SYS (2), ATI Radeon (1), ATI atillk64.sys (1), Athlon (9), CPU (50), Display Driver (1), Driver (1), EPYC (73), EPYC Server (3), Extension to Linux hwmon Service (1), Generic Encapsulated Software Architecture (1), Graphics Driver (17), Link (1), NUC M15 Laptop Kit Management Engine Driver Pack (1), OverDrive (1), Platform Security Processor (3), Prof Tool (1), Radeon (3), Radeon DirectX 11 Driver (3), Radeon Graphics Driver (1), Radeon Settings Installer (1), Ryzen (32), Ryzen Master (1), Ryzen Mobile (3), Ryzen Pro (6), Trusted Platform Module (1), VBIOS Flash Tool SDK (1), fglrx-driver (2), uProf (2), μProf (3)

PublishedBaseTempVulnerabilityProdExpRemCTIEPSSCVE
10/17/20236.66.6AMD Radeon Graphics Driver IOCTL Request Local Privilege EscalationHardware Driver SoftwareNot DefinedNot Defined0.63-0.00000CVE-2023-20598
09/20/20234.44.4AMD Ryzen DXE Driver information disclosureUnknownNot DefinedNot Defined0.110.00043CVE-2023-20597
09/20/20233.83.8AMD Ryzen/EPYC DXE Driver information disclosureUnknownNot DefinedNot Defined0.720.00043CVE-2023-20594
08/08/20235.15.1AMD Ryzen denial of serviceUnknownNot DefinedNot Defined0.030.00043CVE-2023-20560
08/08/20235.55.5AMD Ryzen Privilege EscalationUnknownNot DefinedNot Defined0.030.00042CVE-2023-20564
08/08/20235.55.5AMD EPYC/Athlon/Ryzen divide by zeroUnknownNot DefinedNot Defined0.030.00048CVE-2023-20588
08/08/20236.66.6AMD μProf IOCTL data authenticityUnknownNot DefinedNot Defined0.040.00042CVE-2023-20562
08/08/20235.35.3AMD Ryzen ASP Secure Boot injectionUnknownNot DefinedNot Defined0.030.00055CVE-2023-20589
08/08/20234.54.5AMD μProf IOCTL denial of serviceUnknownNot DefinedNot Defined0.030.00043CVE-2023-20561
08/08/20236.66.6AMD Ryzen/Athlon SMM CpmDisplayFeatureSmm memory corruptionUnknownNot DefinedNot Defined0.050.00042CVE-2023-20555
08/08/20237.57.5AMD Radeon Local Privilege EscalationUnknownNot DefinedNot Defined0.040.00091CVE-2023-20586
08/08/20233.53.5AMD μProf IOCTL denial of serviceUnknownNot DefinedNot Defined0.000.00043CVE-2023-20556
08/01/20232.62.6AMD Ryzen/EPYC information exposureUnknownNot DefinedNot Defined0.030.00043CVE-2023-20583
07/24/20234.44.3AMD Ryzen/EPYC Vector Register File Zenbleed use after freeUnknownNot DefinedOfficial Fix0.000.00057CVE-2023-20593
07/11/20234.54.5AMD EPYC SEV VM observable behavioral discrepancyUnknownNot DefinedNot Defined0.000.00054CVE-2023-20575
05/09/20236.66.6AMD EPYC SMM denial of serviceUnknownNot DefinedNot Defined0.030.00046CVE-2021-46765
05/09/20236.56.5AMD EPYC VM_HSAVE_PA memory corruptionUnknownNot DefinedNot Defined0.000.00047CVE-2022-23818
05/09/20234.64.6AMD EPYC SMU memory corruptionUnknownNot DefinedNot Defined0.040.00046CVE-2021-46764
05/09/20236.86.8AMD EPYC SMU denial of serviceUnknownNot DefinedNot Defined0.000.00047CVE-2021-46762
05/09/20237.17.1AMD EPYC ASP Memory memory corruptionUnknownNot DefinedNot Defined0.000.00067CVE-2021-46773
05/09/20237.17.1AMD EPYC ASP Bootloader input validationUnknownNot DefinedNot Defined0.040.00067CVE-2021-46769
05/09/20235.15.1AMD EPYC TEE input validationUnknownNot DefinedNot Defined0.030.00055CVE-2021-46759
05/09/20235.45.4AMD EPYC ABL memory corruptionUnknownNot DefinedNot Defined0.000.00054CVE-2021-46775
05/09/20236.06.0AMD EPYC System Management Interface out-of-boundsUnknownNot DefinedNot Defined0.000.00046CVE-2021-46794
05/09/20235.35.3AMD EPYC toctouUnknownNot DefinedNot Defined0.000.00046CVE-2021-46792

181 more entries are not shown

Do you need the next level of professionalism?

Upgrade your account now!