AMD Driver Pixel Shader ATIDXX64.DLL memory corruption – Digitalmunition

Exploit/Advisories Cybersecurity study of the dark web exposes vulnerability to machine identities -- ScienceDaily

Published on December 6th, 2019 📆 | 7045 Views ⚑


AMD Driver Pixel Shader ATIDXX64.DLL memory corruption

CVSS Meta Temp ScoreCurrent Exploit Price (≈)CTI Interest Score

A vulnerability has been found in AMD Driver (Hardware Driver Software) (affected version unknown) and classified as critical. Affected by this vulnerability is an unknown code in the library ATIDXX64.DLL of the component Pixel Shader. The manipulation with an unknown input leads to a memory corruption vulnerability (Out-of-Bounds). The CWE definition for the vulnerability is CWE-119. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was released 12/05/2019. This vulnerability is known as CVE-2019-5098 since 01/04/2019. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/06/2019).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.




VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5

VulDB Base Score: ≈5.5
VulDB Temp Score: ≈5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Class: Memory corruption / Out-of-Bounds (CWE-119)
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

Price Prediction: 🔍
Current Price Estimation: 🔒

Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍Recommended: no mitigation known

0-Day Time: 🔒

01/04/2019 CVE assigned
12/05/2019 +335 days Advisory disclosed
12/06/2019 +1 days VulDB entry created
12/06/2019 +0 days VulDB last update
CVE: CVE-2019-5098 (🔒)Created: 12/06/2019 07:43 AM
Complete: 🔍

Download the whitepaper to learn more about our service!

Tagged with:

Leave a Reply ✍