We live in a new era where identity has changed. It’s fractured. Identity is no longer solely issued by our governments in the form of a birth certificate, driver's license, passport or tax ID. Instead, every person creates their own online identities to interact with others and gain access to their digital world. Each one of us now has dozens, even hundreds of identities, so it’s impossible to easily verify the real person behind an online identity. Compounding the challenge, constant data breaches feed the explosion of identity crime by letting any fraudster abuse the personal data found in a typical credit file.
Today we are in a state where no one can trust an online identity and no organization can protect our identities from being exposed. We call this current state of the world The Global Identity Crisis.
Pipl exists to solve the global identity crisis.
Pipl looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.
Pipl will make a best effort to meet the following SLAs for hackers participating in our program:
We’ll try to keep you informed about our progress throughout the process.
- As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
- Please use your @wearehackerone email alias when creating test accounts.
- Feel free to take a look at our developer documentation: https://docs.pipl.com/docs
Out of scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Clickjacking on pages with no sensitive actions.
- Unauthenticated logout/login CSRF.
- Attacks requiring MITM or physical access to a user's device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Comma Separated Values (CSV) injection without demonstrating a vulnerability.
- Missing Best Practice, Configuration or Policy Suggestions including SSL/TLS configurations.
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Output from Automated Scanners without a PoC to demonstrate a specific vulnerability
- Rate limiting or bruteforce issues on non-authentication endpoints
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
- Issues that require unlikely user interaction
- Lack of Secure or HTTP only flag on non-sensitive cookies
- Social engineering of Pipl employees, contractors, vendors, or service providers.
- Physical attacks against Pipl employees, offices, and data centers.
- Any Denial of Service attacks against Pipl and our products.
- Any vulnerability obtained through the compromise of a Pipl customer or employee account. Please create a free account to test potential vulnerabilities.
- Any 3rd party vendor that Pipl uses
- Attacks against the integrity of Pipl customers.
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep Pipl and our users safe!