You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"summary": "GPU-Z.sys, part of the GPU-Z package from TechPowerUp, exposes the wrmsr instruction to user-mode callers without properly validating the target Model Specific Register (MSR). This can result in arbitrary unsigned code being executed in Ring 0.",
GPU-Z.sys, part of the GPU-Z package from TechPowerUp, exposes the wrmsr instruction to user-mode callers without properly validating the target Model Specific Register (MSR). This can result in arbitrary unsigned code being executed in Ring 0.
4
+
5
+
## Impact
6
+
High - Arbitrary Ring 0 code execution
7
+
8
+
## Exploitability
9
+
Medium/Low - Driver must be loaded or attacker will require admin rights. Newer versions require admin callers.
10
+
11
+
## CVE Reference
12
+
CVE-2019-7245
13
+
14
+
## Technical Details
15
+
IOCTL 0x8000644C in the GPU-Z driver instructs the binary to modify a Model Specific Register (MSR) on the target system. These registers control a wide variety of system functionality and can be used to monitor CPU temperature, track branches in code, tweak voltages, etc. MSRs are also responsible for setting the kernel mode function responsible for handling system calls.
16
+
17
+
The driver does not appropriately filter access to MSRs, allowing an attacker to overwrite the system call handler and run unsigned code in Ring 0. Allowing access to any of the following MSRs can result in arbitrary Ring 0 code being executed:
18
+
19
+
* 0xC0000081
20
+
* 0xC0000082
21
+
* 0xC0000083
22
+
* 0x174
23
+
* 0x175
24
+
* 0x176
25
+
26
+
For exploitation details see the INFILTRATE presentation in the references.
27
+
28
+
## Resolution
29
+
This issue is fixed in v2.23.0: [https://www.techpowerup.com/257995/techpowerup-releases-gpu-z-v2-23-0](https://www.techpowerup.com/257995/techpowerup-releases-gpu-z-v2-23-0)
30
+
31
+
## Discovery Credits
32
+
Ryan Warns
33
+
34
+
## Disclosure Timeline
35
+
- 2 February 2019 - Contacted vendor
36
+
- 2 February 2019 - Vendor response, confirmation of issue
Digi International's ConnectPort X2e is susceptible to a local privilege escalation vulnerable to the privileged user `root`.
5
+
6
+
## Impact
7
+
High - An attacker with remote network access to a X2e could remotely compromise the device. This could be used to install malware, modify system behavior, or stage a more serious attack.
8
+
9
+
## Exploitability
10
+
Medium - An attacker would need to read and write files as the system user python. On production devices, this can be accomplished remotely by establishing an SSH connection or access via a TTY.
11
+
12
+
## CVE Reference
13
+
CVE-2020-12878
14
+
15
+
## Technical Details
16
+
The ConnectPort X2e performed filesystem actions as the privileged system user root on files controllable by the less-privileged user python. A malicious attacker could use this to escalate privileges from the local user `python` user to `root`.
17
+
18
+
Mandiant determined that the user `root` executed the file `/etc/init.d/S50dropbear.sh` during normal system boot. The shell script performed a `chown` on the directory `/WEB/python/.ssh/`, which was writable as the user `python`.
19
+
20
+
To exploit this, Mandiant used Linux symbolic links to force the system to set the ownership of the directory `/etc/init.d/` to `python:python`. Mandiant could then create a malicious `init` script in the `/etc/init.d/` directory that would be executed by `root` on future system boots.
21
+
22
+
## Resolution
23
+
Digi International has fixed the reported vulnerability in [version 3.2.30.6](https://ftp1.digi.com/support/firmware/93001304_D.pdf) (May 2020) of the ConnectPort X2e software.
24
+
25
+
## Discovery Credits
26
+
- Jake Valletta, FireEye Mandiant
27
+
- Sam Sabetan, FireEye Mandiant
28
+
29
+
## Disclosure Timeline
30
+
31
+
- 13 February 2020 - Issue reported to vendor
32
+
- 11 March 2020 - Issue confirmed by Digi International
33
+
- 14 May 2020 - CVE reserved with MITRE
34
+
- May 2020 - Digi Releases Patch
35
+
- 17 February 2021 - FireEye Mandiant advisory published
0 commit comments