SnapNames Bug Bounty

Description

No technology is perfect, and SnapNames believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. We are excited for you to participate as a security researcher to help us identify vulnerabilities in our targets. Good luck and happy hunting! Eligibility You may not participate in this program if you are an employee or family member of an employee, or a current vendor or employee of such vendor of Newfold Digital and any of its subsidiaries. You are also prohibited from participating if you are (i) in a country or territory that is the target of U.S. sanctions (including Cuba, Iran, Syria, North Korea, or the Crimea region of Ukraine), (ii) designated as a Specially Designated National or Blocked Person by the U.S. Department of the Treasury’s Office of Foreign Assets Control or otherwise owned, controlled, or acting on behalf of such a person or entity, or (iii) otherwise a prohibited party under U.S. trade and export control laws. Ratings/Rewards The program relies on CVSS to evaluate impact and determine reward allocations. It is essential to highlight that the priority of a vulnerability might be altered due to following: The severity of the vulnerability (CVSS rating) The likelihood of exploit The impact of exploit Any other factor at our discretion CVSS Score │ VRT Classification 9.0-10.0 │ P1-Critical 7.0-8.9 │ P2-High 4.0-6.9 │ P3-Medium 2.0-3.9 │ P4-Low 0.0-1.9 │ P5-Informational We reserve the right to make any final determination of rating levels for any reported vulnerability. Researchers must provide a fully working non-malicious proof of concept that demonstrates a valid security impact to qualify for rewards.

Targets

Credentials You are able to self-sign up for credentials. You will need a credit card in order to do so. Please note that gift cards may not work as the sign up process requires: Two temporary holds placed on your credit card, under $2.00, from Snapnames.com. Please provide these amounts. Those amounts will drop off in 3-5 days. If you do not see these holds, you may need to contact your bank/card provider and request they provide them to you. For additional security, secondary verification is now required on all accounts. For this, we require the following: A copy of a valid, government-issued photo identification (front and back) which matches the name on the account. An image of you in possession of said identification. Please be sure to include your face in this image so that we may confirm your identity. You can send this to [email protected]. Program Rules Do not create multiple accounts for testing purposes within SnapNames applications and services. Refrain from using brute force techniques to assess API rate limiting or other functionalities. Phishing, vishing, smishing, or any other forms of social engineering are strictly prohibited. Ensure efforts are made to avoid privacy violations, data destruction, and disruption or degradation of service. Only interact with accounts you own or have explicit permission to use. Unblocking restricted accounts is not guaranteed. Requests for review can be submitted through Bugcrowd for consideration by the SnapNames InfoSec team. Testing is only permitted on components directly controlled by our program; third-party assets are excluded. Vulnerabilities found on different domains/target may be controlled by the same platform code. If you find the same bug on a different target, prior to the report reaching a triaged state, file it within the existing report. Any reports filed separately while we are actively working to resolve the issue will be treated as a duplicate. Interacting with real customers or real customer accounts is forbidden. When a vulnerability consists of different parameters but having the same endpoint, please group this together in the same report else will be considered as duplicate. Multiple vulnerabilities caused by one underlying issue will be awarded one bounty (Ex: Centralized vulnerable parameters). Cross-Site Scripting (XSS) attacks are considered at maximum a medium severity. Out of Scope Do not test the support functionality Subdomain takeovers. Please submit any subdomain takeovers to the SnapNames VDP . Cache poisoning No DMARC, nor SPF Dos/DDos (Rate Limiting) OAuth session token is not invalidated on logout or password change/reset Open redirect vulnerabilities Error messages (e.g. verbose error messages, stack traces, application or server errors, version disclosure) Clickjacking Missing or misconfigured HTTP security header HTTP/DNS cache poisoning Cloudflare related issues Self-XSS reports will not be accepted Broken links hosted on our website Secrets such as API keys or passwords obtained from external aggregation/indexed data sources (e.g., dehashed.com or intelx.io) Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with non-sensitive actions (including logout CSRF) Recently disclosed (<30 days) zero-day vulnerabilities Please do not test chatboxes on the applications, etc. Use of third-party vulnerable components Anti Automation attacks, missing captcha, missing rate limiting, HTTP headers, SSL/TLS configuration and missing Secure flag on cookies are out of scope Any source code disclosure Info.php (without providing an exploitable scenario) Safe Harbor When conducting vulnerability research according to this policy, we consider this research to be: Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy; Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls; Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and Lawful, helpful to the overall security of the Internet, and conducted in good faith. You are expected, as always, to comply with all applicable laws. If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire via Bugcrowd Support before going any further.

In Scope (in scope)

Target Information Aftermarket domain name applications like SnapNames and NameJet help businesses and individuals acquire previously owned domain names that are expiring or about to be deleted. By leveraging exclusive partnerships with top registrars and using advanced technology, they monitor and capture high-demand domain names before others can. This service ensures clients get the best chance to secure valuable or brand-specific domain names even if they are already taken.

Out Of Scope (out of scope)

Any asset not explicitly listed in scope above falls outside this program. If you have found a vulnerability on an asset not covered here, we still want to hear from you — please submit it through our Vulnerability Disclosure Program using the relevant link below: Namejet Snapnames BuyDomains Reports submitted through these forms will be reviewed by our security team.