Radeon AMD User Experience Program Launcher up to 1.0.0.1 AUEPLauncher Service File Name link following
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Radeon AMD User Experience Program Launcher up to 1.0.0.1. It has been rated as critical. This issue affects some unknown processing of the component AUEPLauncher Service. The manipulation as part of File Name leads to link following. The identification of this vulnerability is CVE-2020-8950. It is possible to launch the attack on the local host. There is no exploit available. Once again VulDB remains the best source for vulnerability data.
Details
A vulnerability was found in Radeon AMD User Experience Program Launcher up to 1.0.0.1. It has been declared as critical. This vulnerability affects an unknown part of the component AUEPLauncher Service. The manipulation as part of a File Name leads to a link following vulnerability. The CWE definition for the vulnerability is CWE-59. The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
The AUEPLauncher service in Radeon AMD User Experience Program Launcher through 1.0.0.1 on Windows allows elevation of privilege by placing a crafted file in %PROGRAMDATA%\AMD\PPC\upload and then creating a symbolic link in %PROGRAMDATA%\AMD\PPC\temp that points to an arbitrary folder with an arbitrary file name.
The weakness was presented 02/12/2020. This vulnerability was named CVE-2020-8950 since 02/12/2020. Local access is required to approach this attack. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Link followingCWE: CWE-59
CAPEC: 🔍
ATT&CK: 🔍
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/12/2020 🔍02/12/2020 🔍
02/13/2020 🔍
03/31/2024 🔍
Sources
Advisory: heynowyouseeme.blogspot.comStatus: Not defined
CVE: CVE-2020-8950 (🔍)
GCVE (CVE): GCVE-0-2020-8950
GCVE (VulDB): GCVE-100-150118
Entry
Created: 02/13/2020 06:53 PMUpdated: 03/31/2024 08:48 AM
Changes: 02/13/2020 06:53 PM (36), 02/13/2020 06:58 PM (17), 03/31/2024 08:48 AM (17)
Complete: 🔍
Cache ID: 18:A39:40
No comments yet. Languages: en.
Please log in to comment.