Lucene search
K

7 matches found

CNVD
CNVD
added 2020/10/29 12:0 a.m.1 views

Pulse Secure Desktop Client Client Registry Elevation of Privilege Vulnerability

Pulse Secure Desktop Client is scalable, multi-service network client that supports integrated connectivity and secure location-aware network access. A client registry privilege escalation vulnerability exists in Pulse Secure Desktop Client Linux versions prior to 9.1R9, which originates in the...

9.8CVSS6.5AI score0.00433EPSS
Exploits1References1
OSV
OSV
added 2020/10/28 1:15 p.m.1 views

CVE-2020-8239

A vulnerability in the Pulse Secure Desktop Client 9.1R9 is vulnerable to the client registry privilege escalation attack. This fix also requires Server Side Upgrade due to Standalone Host Checker Client Windows and Windows PDC...

9.8CVSS6.4AI score
Exploits0References1
NVD
NVD
added 2020/10/28 1:15 p.m.16 views

CVE-2020-8239

A vulnerability in the Pulse Secure Desktop Client 9.1R9 is vulnerable to the client registry privilege escalation attack. This fix also requires Server Side Upgrade due to Standalone Host Checker Client Windows and Windows PDC...

9.8CVSS9.5AI score0.00433EPSS
Exploits1References1
Prion
Prion
added 2020/10/28 1:15 p.m.11 views

Privilege escalation

A vulnerability in the Pulse Secure Desktop Client 9.1R9 is vulnerable to the client registry privilege escalation attack. This fix also requires Server Side Upgrade due to Standalone Host Checker Client Windows and Windows PDC...

7.5CVSS9.4AI score0.00433EPSS
Exploits1References1Affected Software1
Cvelist
Cvelist
added 2020/10/28 12:46 p.m.16 views

CVE-2020-8239

A vulnerability in the Pulse Secure Desktop Client 9.1R9 is vulnerable to the client registry privilege escalation attack. This fix also requires Server Side Upgrade due to Standalone Host Checker Client Windows and Windows PDC...

9.5AI score0.00433EPSS
Exploits1References1
Veeam
Veeam
added 2012/10/01 12:0 a.m.24 views

Time difference between Veeam Monitor server and ESX host is too large.

Challenge When attempting to add a vCenter Server or a standalone host with a different time zone, the operation may fail with the error: Failed to connect to "". Time difference between Veeam Monitor server and ESX host is too large. Make sure that NTP is enabled on ESX host and try again. Cause...

7AI score
Exploits0Affected Software1
Veeam
Veeam
added 2012/07/09 12:0 a.m.10 views

Monitoring of standalone hosts fails

Challenge No topology is created for standalone ESX/ESXi hosts. nworks logs contain the following errors: 0.0017 EXCOL+ VP120 retrieveHostProperties failed, buildMorList: zero count at nworksCore.Collectors.VimUtil.buildMorListList1 nodes at...

6.8AI score
Exploits0
Rows per page
Query Builder