PingID Windows Login prior to 2.8 does not alert or halt operation if it has been provisioned with the full permissions PingID properties file. An IT administrator could mistakenly deploy administrator privileged PingID API credentials, such as those typically used by PingFederate, into PingID Windows Login user endpoints. Using sensitive full permissions properties file outside of a privileged trust boundary leads to an increased risk of exposure or discovery, and an attacker could leverage these credentials to perform administrative actions against PingID APIs or endpoints.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:HPingidentity Pingid Integration For Windows Login
APPPingidentity< 2.8
Related vulnerabilities
PingID Windows Login prior to 2.8 does not properly set permissions on the Windows Registry entries used to st...
PingID Windows Login prior to 2.8 uses known vulnerable components that can lead to remote code execution. An ...
PingID Windows Login prior to 2.8 does not authenticate communication with a local Java service used to captur...
A misconfiguration of RSA in PingID Windows Login prior to 2.7 is vulnerable to pre-computed dictionary attack...
PingID Integration for Windows Login before 2.4.2 allows local users to gain privileges by modifying CefSharp....