cbcvebase.
CVE-2017-9769
published 2017-08-02

CVE-2017-9769: A specially crafted IOCTL can be issued to the rzpnk.sys driver in Razer Synapse 2.20.15.1104 that is forwarded to ZwOpenProcess allowing a handle to be opened…

PriorityP275critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EXPLOIT
EPSS
85.54%
99.7th percentile
A specially crafted IOCTL can be issued to the rzpnk.sys driver in Razer Synapse 2.20.15.1104 that is forwarded to ZwOpenProcess allowing a handle to be opened to an arbitrary process.

Affected

1 ranges
VendorProductVersion rangeFixed in
razersynapse

Detection & IOCsextracted from sources · hover to see the quote

filenamerzpnk.sys
hashb4598c05d5440250633e25933fff42b0
other\\.\47CD78C9-64C3-47C2-B80F-677B887CF095
other0x22a050
processRazerIngameEngine.exe
  • Monitor for processes issuing DeviceIoControl calls to the device path \\.\47CD78C9-64C3-47C2-B80F-677B887CF095 (rzpnk.sys) with IOCTL code 0x22a050, which is the vulnerable handler that forwards a user-supplied PID to ZwOpenProcess.
  • Alert on non-system processes opening a handle to winlogon.exe with PROCESS_VM_WRITE / PROCESS_VM_OPERATION access rights, especially following interaction with rzpnk.sys.
  • Detect termination of RazerIngameEngine.exe by a non-Razer process; the exploit explicitly kills this process before issuing the malicious IOCTL.
  • Detect calls to user32!LockWorkStation() originating from unusual processes or shellcode context; the exploit triggers its hook by calling this function to execute payload in winlogon.
  • Verify the MD5 hash of the loaded rzpnk.sys driver; the known-vulnerable version has MD5 b4598c05d5440250633e25933fff42b0.
  • ·Exploitation only works on 64-bit Windows targets (x64 architecture); the Metasploit module explicitly rejects non-x64 sessions.
  • ·The malicious IOCTL (0x22a050) will fail if RazerIngameEngine.exe is running at the time of exploitation; the exploit must kill it first.
  • ·The exploit is not opsec-safe; the user will be logged out as part of the exploitation process, making it noisy and detectable via session/logoff events.
  • ·No Razer hardware needs to be physically connected for the vulnerability to be exploitable; presence of the driver alone is sufficient.

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.010.0CRITICALAV:N/AC:L/Au:N/C:C/I:C/A:C
CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.