Skip to content

Product

razer synapse vulnerabilities

12 published CVES affecting razer synapse, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
12
Critical
1
High
8
Medium
3
Low
0
Unscored
0
CISA KEV
0

Latest razer synapse CVEs

Newest publication first

  1. HighCVSS 7.8 EPSS 0.39%

    Razer Synapse through 3.7.1209.121307 allows privilege escalation due to an unsafe installation path and improper privilege management. Attackers can place DLLs into %PROGRAMDATA%\Razer\Synapse3\Service\bin if they do so before the service is installed and if they deny write acce...

  2. MediumCVSS 6.8 EPSS 0.65%

    Razer Synapse before 3.7.0830.081906 allows privilege escalation due to an unsafe installation path, improper privilege management, and improper certificate validation. Attackers can place malicious DLLs into %PROGRAMDATA%\Razer\Synapse3\Service\bin if they do so before the servi...

  3. HighCVSS 7.3 EPSS 0.90%

    Razer Synapse before 3.7.0228.022817 allows privilege escalation because it relies on %PROGRAMDATA%\Razer\Synapse3\Service\bin even if %PROGRAMDATA%\Razer has been created by any unprivileged user before Synapse is installed. The unprivileged user may have placed Trojan horse DLL...

  4. MediumCVSS 5.5 EPSS 0.50%

    Multiple system services installed alongside the Razer Synapse 3 software suite perform privileged operations on entries within the Razer Chroma SDK subkey. These privileged operations consist of file name concatenation of a runtime log file that is used to store runtime log info...

  5. MediumCVSS 5.5 EPSS 0.52%

    Multiple system services installed alongside the Razer Synapse 3 software suite perform privileged operations on entries within the ChromaBroadcast subkey. These privileged operations consist of file name concatenation of a runtime log file that is used to store runtime log infor...

  6. HighCVSS 7.8 EPSS 0.29%

    rzpnk.sys in Razer Synapse 2.20.15.1104 allows local users to read and write to arbitrary memory locations, and consequently gain privileges, via a methodology involving a handle to \Device\PhysicalMemory, IOCTL 0x22A064, and ZwMapViewOfSection.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.