Ping Identity vulnerabilities, page 2

53 vulnerabilities

Known vulnerabilities in Ping Identity products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 28 products.

7.7CVE-2022-40722ping identitypingfederate (includes pingid adapter)+5
EPSS score
0.33%
A misconfiguration of RSA padding implemented in the PingID Adapter for PingFederate to support Offline MFA with PingID mobile authenticators is vulnerable to pre-computed dictionary attacks, leading to a bypass of offline MFA.
8.1CVE-2022-23724ping identitypingid integration for windows login+1
EPSS score
0.45%
Use of static encryption key material allows forging an authentication token to other users within a tenant organization. MFA may be bypassed by redirecting an authentication flow to a target user. To exploit the vulnerability, must have compromised user credentials.
7.7CVE-2022-23723ping identitypingfederate pingone mfa integration kit+1
EPSS score
0.88%
An MFA bypass vulnerability exists in the PingFederate PingOne MFA Integration Kit when adapter HTML templates are used as part of an authentication flow.
9.3CVE-2022-23718ping identitypingid windows login+1
EPSS score
2.09%
PingID Windows Login prior to 2.8 uses known vulnerable components that can lead to remote code execution. An attacker capable of achieving a sophisticated man-in-the-middle position, or to compromise Ping Identity web servers, could deliver malicious code that would be executed as SYSTEM by the PingID Windows Login application.
7.7CVE-2022-23725ping identitypingid windows login+1
EPSS score
0.21%
PingID Windows Login prior to 2.8 does not properly set permissions on the Windows Registry entries used to store sensitive API keys under some circumstances.
8.2CVE-2022-23720ping identitypingid windows login+1
EPSS score
0.24%
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.
6.5CVE-2022-23722ping identitypingfederate+1
EPSS score
0.61%
When a password reset mechanism is configured to use the Authentication API with an Authentication Policy, email One-Time Password, PingID or SMS authentication, an existing user can reset another existing user’s password.
5.5CVE-2022-23717ping identitypingid windows login+1
EPSS score
0.23%
PingID Windows Login prior to 2.8 is vulnerable to a denial of service condition on local machines when combined with using offline security keys as part of authentication.
5.4CVE-2022-23726ping identitypingcentral+1
EPSS score
0.70%
PingCentral versions prior to listed versions expose Spring Boot actuator endpoints that with administrative authentication return large amounts of sensitive environmental and application information.
7.2CVE-2022-23719ping identitypingid windows login+1
EPSS score
0.29%
PingID Windows Login prior to 2.8 does not authenticate communication with a local Java service used to capture security key requests. An attacker with the ability to execute code on the target machine maybe able to exploit and spoof the local Java service using multiple attack vectors. A successful attack can lead to code executed as SYSTEM by the PingID Windows Login application, or even a denial of service for offline security key authentication.
3.8CVE-2022-23721ping identityunspecified+1
EPSS score
0.22%
PingID integration for Windows login prior to 2.9 does not handle duplicate usernames, which can lead to a username collision when two people with the same username are provisioned onto the same machine at different times.
3.5CVE-2024-21832ping identitypingfederate
EPSS score
0.24%
A potential JSON injection attack vector exists in PingFederate REST API data stores using the POST method and a JSON request body.
6.1CVE-2024-25566forgerockaccess_management+1
EPSS score
0.24%
An Open-Redirect vulnerability exists in PingAM where well-crafted requests may cause improper validation of redirect URLs. This could allow an attacker to redirect end-users to malicious sites under their control, simplifying phishing attacks
6.9CVE-2024-25573ping identitypingfederate
EPSS score
0.37%
Unsanitized user-supplied data saved in the PingFederate Administrative Console could trigger the execution of JavaScript code in subsequent user processing.
4.3CVE-2024-22477ping identitypingfederate+1
EPSS score
0.17%
A cross-site scripting vulnerability exists in the admin console OIDC Policy Management Editor. The impact is contained to admin console users only.
5.3CVE-2024-22377ping identitypingfederate+1
EPSS score
0.44%
The deploy directory in PingFederate runtime nodes is reachable to unauthorized users.
2.7CVE-2024-23600ping identitypingidm
EPSS score
0.67%
Improper Input Validation of query search results for private field data in PingIDM (Query Filter module) allows for a potentially efficient brute forcing approach leading to information disclosure.
8.8CVE-2024-23316ping identitypingaccess
EPSS score
0.55%
HTTP request desynchronization in Ping Identity PingAccess, all versions prior to 8.0.1 affected allows an attacker to send specially crafted http header requests to create a request smuggling condition for proxied requests.
5.8CVE-2024-23983ping identitypingaccess
EPSS score
0.43%
Improper handling of canonical URL-encoding may lead to bypass not properly constrained by request rules.
9.5CVE-2026-21391ping identitypingam
EPSS score
0.45%
An improper validation vulnerability exists within PingAM where a well-crafted request allows arbitrary or protected ID Token claims to be set or overridden. In certain configurations this could allow an attacker to bypass authentication controls via spoofing leading to privilege escalation or impersonation.