- Top reward
- $2,400
- Top severity paid
- Critical
- Assets in scope
- 10
- Public CVEs
- 39
- Last change
At a glance
What to know before you start testing.
- Pays up to $2,400
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Replies within 5 days
- As the policy promises.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$2,400 |
| High |
|
$1,200 |
| Medium |
|
$600 |
| Low |
|
$300 |
- Response
-
Within 5 days
First response - 5 business days from submission
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
10 assets you may test, 16 excluded.
Web 6
- api.ort-one-pingone.com Critical
- apps.ort-one-pingone.com Critical
- auth.ort-one-pingone.com Critical
- console.ort-one-pingone.com Critical
- https://console.ort-one-pingone.com/?env=361b34ef-2725-4fd9-af1b-a2b189df3d05 Critical
- https://console.ort-one-pingone.com/?env=7f327541-54e0-4ba4-8335-65eac2a25b5e Critical
Wildcard domains 4
- openam-bug-bounty-stag.forgeblocks.com/* Critical
- ort-admin.pingone.com/* Critical
- ort-authenticator.pingone.com/* High
- ort-desktop.pingone.com/* High
Out of scope (16)
- admin.pingone.com
- api.pingone.com
- api-staging.pingone.com
- authenticator.pingone.com
- console.pingone.com
- console-staging.pingone.com
- desktop.pingone.com
- privilege.ort-one-pingone.com
- test-desktop.pingone.com
- test-sso.connect.pingidentity.com
- uploads.pingone.com
- uploads-staging.pingone.com
- developer.pingidentity.com/*
- *.pingidentity.com
- *.pingidentity.io
- *.pingidentity.net
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Ping Identity (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue is not eligible for a reward.
-
Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
-
When duplicates occur, we only award the first eligible report that we receive.
-
When multiple vulnerabilities are caused by one underlying issue, we award a single bounty.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
-
Avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or have explicit permission to interact with.
Not accepted
-
Session mismanagement on change or forget password
-
Publicly exposed Google Maps API key
-
Publicly exposed New Relic monitoring access token
-
Publicly exposed Coveo search access token
-
Missing SPF Records
-
Issues without clearly identified security impact or with only speculative theoretical exploitability
-
Self-exploitation (cookie reuse, self cookie-bomb, self denial-of-service, etc.)
-
Self Cross-Site Scripting vulnerabilities without evidence of how the vulnerability can be used to attack another user
-
Missing best practices in SSL/TLS configuration
-
Any activity that could lead to the disruption of our service (DoS), the brute forcing of credentials, or the cracking of licenses
-
Attacks requiring MitM or physical access to a user's device
-
Subdomains lacking proper SPF records
-
Clickjacking on pages with no sensitive actions
-
Unauthenticated/logout/login CSRF
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability
-
Content-spoofing and text injection issues without showing an attack vector or without being able to modify HTML/CSS
-
Social engineering of Ping Identity employees or contractors
-
Leaked credentials collected from the dark web, breach databases, etc.
-
Any physical/wireless attempt against Ping Identity property
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 43 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope added
https://developer.pingidentity.com/* (out of scope)
-
Scope added
https://ort-authenticator.pingone.com/*
-
Scope added
https://ort-desktop.pingone.com/*
-
Scope added
https://openam-bug-bounty-stag.forgeblocks.com/*
-
Scope added
https://ort-admin.pingone.com/*
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2024-22377 | The deploy directory in PingFederate runtime nodes is reachable to unauthorized users. | Medium 5.3 | 9 Jul 2024 |
| CVE-2024-22477 | A cross-site scripting vulnerability exists in the admin console OIDC Policy Management Editor. The impact is contained to admin console users only. | Low 1.8 | 9 Jul 2024 |
| CVE-2023-40545 | Authentication bypass when an OAuth2 Client is using client_secret_jwt as its authentication method on affected 11.3 versions via specially crafted requests. | High 8.8 | 6 Feb 2024 |
| CVE-2023-36496 | Delegated Admin Privilege virtual attribute provider plugin, when enabled, allows an authenticated user to elevate their permissions in the Directory Server. | High 7.7 | 1 Feb 2024 |
| CVE-2023-39930 | A first-factor authentication bypass vulnerability exists in the PingFederate with PingID Radius PCV when a MSCHAP authentication request is sent via a maliciously crafted RADIUS client request. | High 7.5 | 25 Oct 2023 |
| CVE-2023-39219 | PingFederate Administrative Console dependency contains a weakness where console becomes unresponsive with crafted Java class loading enumeration requests | High 7.5 | 25 Oct 2023 |
| CVE-2023-39231 | PingFederate using the PingOne MFA adapter allows a new MFA device to be paired without requiring second factor authentication from an existing registered device. A threat actor may be able to exploit this vulnerability to register their own MFA device if they have knowledge of a victim user's first factor credentials. | High 7.3 | 25 Oct 2023 |
| CVE-2023-34085 | When an AWS DynamoDB table is used for user attribute storage, it is possible to retrieve the attributes of another user using a maliciously crafted request | Low 2.6 | 25 Oct 2023 |
| CVE-2023-37283 | Under a very specific and highly unrecommended configuration, authentication bypass is possible in the PingFederate Identifier First Adapter | High 8.1 | 25 Oct 2023 |
| CVE-2022-23721 | 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. | Low 3.8 | 25 Apr 2023 |
| CVE-2022-40722 | 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. | High 7.7 | 25 Apr 2023 |
| CVE-2022-40723 | The PingID RADIUS PCV adapter for PingFederate, which supports RADIUS authentication with PingID MFA, is vulnerable to MFA bypass under certain configurations. | Medium 6.5 | 25 Apr 2023 |
| CVE-2022-40724 | The PingFederate Local Identity Profiles '/pf/idprofile.ping' endpoint is vulnerable to Cross-Site Request Forgery (CSRF) through crafted GET requests. | Medium 6.4 | 25 Apr 2023 |
| CVE-2022-40725 | PingID Desktop prior to the latest released version 1.7.4 contains a vulnerability that can be exploited to bypass the maximum PIN attempts permitted before the time-based lockout is activated. | High 7.3 | 25 Apr 2023 |
| CVE-2018-25084 | A vulnerability, which was classified as problematic, has been found in Ping Identity Self-Service Account Manager 1.1.2. Affected by this issue is some unknown functionality of the file src/main/java/com/unboundid/webapp/ssam/SSAMController.java. The manipulation leads to cross site scripting. The attack may be launched remotely. Upgrading to version 1.1.3 is able to address this issue. The patch | Low 3.5 | 10 Apr 2023 |
| CVE-2022-23726 | PingCentral versions prior to listed versions expose Spring Boot actuator endpoints that with administrative authentication return large amounts of sensitive environmental and application information. | Medium 5.4 | 30 Sep 2022 |
| CVE-2021-41995 | A misconfiguration of RSA in PingID Mac Login prior to 1.1 is vulnerable to pre-computed dictionary attacks, leading to an offline MFA bypass. | High 7.7 | 30 Jun 2022 |
| CVE-2022-23717 | 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. | Medium 5.0 | 30 Jun 2022 |
| CVE-2022-23718 | 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. | High 7.6 | 30 Jun 2022 |
| CVE-2022-23719 | 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 denia | High 7.2 | 30 Jun 2022 |
| CVE-2022-23720 | 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 tr | High 7.5 | 30 Jun 2022 |
| CVE-2022-23725 | 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. | High 7.7 | 30 Jun 2022 |
| CVE-2022-23724 | 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. | Medium 6.4 | 4 May 2022 |
| CVE-2022-23722 | 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. | Medium 6.5 | 2 May 2022 |
| CVE-2022-23723 | An MFA bypass vulnerability exists in the PingFederate PingOne MFA Integration Kit when adapter HTML templates are used as part of an authentication flow. | High 7.7 | 2 May 2022 |
| CVE-2021-41992 | A misconfiguration of RSA in PingID Windows Login prior to 2.7 is vulnerable to pre-computed dictionary attacks, leading to an offline MFA bypass. | High 7.7 | 30 Apr 2022 |
| CVE-2021-41993 | A misconfiguration of RSA in PingID Android app prior to 1.19 is vulnerable to pre-computed dictionary attacks, leading to an offline MFA bypass when using PingID Windows Login. | Medium 6.6 | 30 Apr 2022 |
| CVE-2021-41994 | A misconfiguration of RSA in PingID iOS app prior to 1.19 is vulnerable to pre-computed dictionary attacks, leading to an offline MFA bypass when using PingID Windows Login. | Medium 6.6 | 30 Apr 2022 |
| CVE-2021-42001 | PingID Desktop prior to 1.7.3 has a misconfiguration in the encryption libraries which can lead to sensitive data exposure. An attacker capable of exploiting this vulnerability may be able to successfully complete an MFA challenge via OTP. | High 8.0 | 30 Apr 2022 |
| CVE-2021-42000 | When a password reset or password change flow with an authentication policy is configured and the adapter in the reset or change policy supports multiple parallel reset flows, an existing user can reset another existing users password. | Medium 5.3 | 10 Feb 2022 |
| CVE-2021-41770 | Ping Identity PingFederate before 10.3.1 mishandles pre-parsing validation, leading to an XXE attack that can achieve XML file disclosure. | High 7.5 | 7 Oct 2021 |
| CVE-2021-40329 | The Authentication API in Ping Identity PingFederate before 10.3 mishandles certain aspects of external password management. | Critical 9.8 | 27 Sep 2021 |
| CVE-2021-31923 | Ping Identity PingAccess before 5.3.3 allows HTTP request smuggling via header manipulation. | Medium 5.3 | 24 Sep 2021 |
| CVE-2021-39270 | In Ping Identity RSA SecurID Integration Kit before 3.2, user impersonation can occur. | High 7.5 | 18 Aug 2021 |
| CVE-2020-25826 | PingID Integration for Windows Login before 2.4.2 allows local users to gain privileges by modifying CefSharp.BrowserSubprocess.exe. | High 7.8 | 23 Sep 2020 |
| CVE-2020-10654 | Ping Identity PingID SSH before 4.0.14 contains a heap buffer overflow in PingID-enrolled servers. This condition can be potentially exploited into a Remote Code Execution vector on the authenticating endpoint. | Critical 9.8 | 13 May 2020 |
| CVE-2019-13564 | XSS exists in Ping Identity Agentless Integration Kit before 1.5. | Medium 6.1 | 11 Jul 2019 |
| CVE-2018-1000134 | UnboundID LDAP SDK version from commit 801111d8b5c732266a5dbd4b3bb0b6c7b94d7afb up to commit 8471904a02438c03965d21367890276bc25fa5a6, where the issue was reported and fixed contains an Incorrect Access Control vulnerability in process function in SimpleBindRequest class doesn't check for empty password when running in synchronous mode. commit with applied fix https://github.com/pingidentity/ldaps | Critical 9.8 | 16 Mar 2018 |
| CVE-2014-8489 | Open redirect vulnerability in startSSO.ping in the SP Endpoints in Ping Identity PingFederate 6.10.1 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the TargetResource parameter. | Medium 6.4 | 12 Dec 2014 |
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Ping Identity looks forward to working with the security community to find and solve vulnerabilities. Thank you for helping us keep our customers safe.
Getting Access
##For our docker images: Please clone this repo and follow the steps in the README. Please use the following credentials for this program:
[email protected]
PING_IDENTITY_DEVOPS_KEY=ed56408c-8d96-6aed-107c-3deb0214e928
You may open an issue in the github repo if you run into trouble.
##For our SaaS offerings: PingOne (console.ort-one-pingone.com): Please obtain credentials via H1 Credential Management for any of the Assets starting with https://console.ort-one-pingone.com/?env=.
PingOne Advanced Identity Cloud (openam-bug-bounty-stag.forgeblocks.com): Self-service account creation:
Initial Sign-up can be achieved through the Account Creation journey: https://openam-bug-bounty-stag.forgeblocks.com/am/XUI/?realm=/alpha&authIndexType=service&authIndexValue=Login#/service/Registration
A valid email address is required for account creation, we prefer that researchers use their HackerOne (@wearehackerone.com) email address whilst registering.
Please limit account creation to 2 user accounts.
NOTE: As per the program scope, neither *.pingidentity.* or *.symphonicsoft.* URLs, nor any other domains or sub-domains registered to Ping Identity that aren't included in our program scope, will be eligible for bounties. Please see in-scope endpoints below. Out of scope reports that are determined to be legitimate vulnerabilities will be remediated, and while they will not be eligible for monetary awards, we will do our best to award as many reputation points as possible to the reporter and publicly disclose actionable reports upon request. If you are a Ping customer, please consider submitting a support ticket here.
Response times
Ping Identity strives to respond to reports as follows:
- First response - 5 business days from submission
- Triage - 10 business days from submission
- Bounty payout - 10 business days from triage
We do our best to keep researchers informed throughout the process.
Disclosure Policy
Follow HackerOne's disclosure guidelines.
Program Rules
- Provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue is not eligible for a reward.
- Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only award the first eligible report that we receive.
- When multiple vulnerabilities are caused by one underlying issue, we award a single bounty.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or have explicit permission to interact with.
#Common vulnerabilities to look for across all endpoints:
- Information disclosure (cluster health, internal hostnames, passwords)
- Exploitable TLS vulnerabilities or misconfiguration
- Components with exploitable security vulnerabilities
- Unauthorized or elevated persistent store access
- Sensitive AWS metadata exposure
- Cross-tenant administrative access or information disclosure
- REST API vulnerabilities
- OWASP Top 10 vulnerabilities
- CWE-SANS Top 25 Dangerous Bugs
#The following issues are well known and ineligible for bounties:
- Session mismanagement on change or forget password
- Publicly exposed Google Maps API key
- Publicly exposed New Relic monitoring access token
- Publicly exposed Coveo search access token
- Missing SPF Records
#The following issues are considered out of scope and ineligible for bounties:
- Ping Identity corporate systems, and neither websites *.pingidentity.* or *.symphonicsoft.*, nor any other domains or sub-domains registered to Ping Identity that are not included in our program scope
- All example code and public repository code at https://github.com/pingidentity or anywhere else on Github, apart from the Docker images in https://github.com/pingidentity/bug-bounty-server-profiles
- All public Docker images at https://hub.docker.com/u/pingidentity that are not part of the repo for bug bounties (https://github.com/pingidentity/bug-bounty-server-profiles)
- All on-premises Ping Identity downloadable products that are not provided in our docker images
- Other Ping Identity customer-downloadable products or components, such as SDKs, including PingID SDK
- Any customizations, Ping Identity adapters, or integration kits
- Issues without clearly identified security impact or with only speculative theoretical exploitability
- Missing security best practices and controls (rate-limiting/throttling, lack of CSRF protection, lack of security headers, missing flags on cookies, descriptive errors, server/technology disclosure, etc.), without a clear and working Proof of Concept
- Self-exploitation (cookie reuse, self cookie-bomb, self denial-of-service, etc.)
- Self Cross-Site Scripting vulnerabilities without evidence of how the vulnerability can be used to attack another user
- Previously known CVEs in third-party services (i.e. Google Tag Manager, New Relic, Coveo, Pendo, etc.), dependencies and open-source libraries (without a clear and working Proof of Concept)
- Missing best practices in SSL/TLS configuration
- Any activity that could lead to the disruption of our service (DoS), the brute forcing of credentials, or the cracking of licenses
- Attacks requiring MitM or physical access to a user's device
- Subdomains lacking proper SPF records
- Clickjacking on pages with no sensitive actions
- Unauthenticated/logout/login CSRF
- Comma Separated Values (CSV) injection without demonstrating a vulnerability
- Content-spoofing and text injection issues without showing an attack vector or without being able to modify HTML/CSS
- Social engineering of Ping Identity employees or contractors
- Leaked credentials collected from the dark web, breach databases, etc.
- Any physical/wireless attempt against Ping Identity property