At NordVPN we strive to maximize the security of our infrastructure and
customers' data. We believe that in order to reach our goal community
participation is essential. Please note that your submission of potential
security vulnerability finding (“Vulnerability Finding”) is voluntary and
subject to the terms and conditions set forth in this Policy. By submitting a
vulnerability to us you acknowledge that you have read and agreed to this
Our main rules are as follows:
- Automated testing is not permitted.
- Follow HackerOne’s Disclosure Guidelines.
- You must be the first person to notify us of a finding that alerts us to a previously unknown issue and that issue triggers a code or configuration change. If different attack vectors result in the same mitigation, NordVPN reserves the right to reward only the first report that is validated for that fix. All subsequent reports that are addressed by that mitigation will be considered as duplicates, regardless of the attack vector. In most instances, you will not be notified of a duplicate report condition until after the vulnerability has been fully remediated.
- We award bounties once the vulnerability is fixed, and will keep you posted as we work to resolve them.
- We reserve the sole right to determine the size of the reward, if any. We determine this on a case by case basis, depending on overall severity (including the business impact, creativity of the issue, etc.). You shall respect our final decision.
- We may pay even higher rewards for, especially clever or severe vulnerabilities. We recommend for you to use Common Vulnerability Scoring System Version 3.0 Calculator as a general guide on vulnerability severity levels. However, please note that this serves only as a rough guide and does NOT guarantee that we will give the same evaluation to your Vulnerability Finding. The final and actual severity level is determined by us in our sole discretion.
- To receive a reward, you must disclose the vulnerability report directly and exclusively to us.
- Previous reward amounts are not considered a precedent for future reward amounts.
- Reward may be denied if there is reason to believe that there has been a violation of this Policy.
You may need to provide additional information, which would be necessary to receive the reward.
Taxes on rewards given to you are your sole responsibility.
- Reward will be forfeited, if it remains unclaimed or undeliverable for a period of six (6) months counting from the date you are notified of the determined reward amount
- Contacting our team regarding the status of a report through any other channel than Hackerone will result in an immediate disqualification for a bounty for that report.
- Please recognize that NordVPN operates complex infrastructure and the amount of time required to address a reported issue can vary from a few hours to several months. You will receive notification of the final outcome of our remediation efforts once the report has been passed to the internal security team. NordVPN cannot provide updates on remediation efforts that are in progress.
This Policy supplements the terms of any other agreement (collectively –
“Agreements”) in which you have entered with us. If any inconsistency exists
between the terms of the Agreements and this Policy, this Policy will prevail,
but only with regard to the potential security vulnerability reporting, unless
otherwise agreed by us in writing.
Scope of Accepted Reports
Accepted, in-scope findings, include, but are not limited to:
- NordVPN consumer applications on all platforms:
- Browser extensions and official apps on third party devices.
- NordVPN VPN servers.
- NordVPN backend services and website.
Out-Of-Scope Reports (not eligible for a reward)
- Findings from physical testing such as office access (e.g. open doors, tailgating).
- Denial of service (DOS) attacks.
- Unofficial third party applications, scripts and integrations.
- End-of-life application versions.
- Vulnerabilities only affecting users of outdated or unpatched browsers and platforms.
- Any other submissions determined to be low risk, based on unlikely or theoretical attack vectors, requiring significant user interaction, or resulting in minimal impact.
- WordPress bugs (please report those to WordPress directly).
- OpenVPN bugs (please report those to OpenVPN directly).
- StrongSwan bugs (please report those to StrongSwan directly).
- Out of date software – we do not always run the most recent software versions (patched).
- Third party services, including but not limited to:
- Anything related to credential stuffing and account takeover.
- Brute force testing to determine whether rate limiting is in place for particular APIs or pieces of functionality (unless it constitutes a significant risk)
- User account verification/enumeration attacks
- User account deletion process
- Findings derived from social engineering (e.g. phishing, vishing, spam) techniques, including:
- SPF and DKIM issues
- Content injection
- Hyperlink injection in emails
- IDN homograph attacks
- RTL Ambiguity
- Content Spoofing
- Issues related to Password Policy
- Missing best practices, information disclosures, use of a known-vulnerable libraries or descriptive / verbose / unique error pages (without substantive information indicating exploitability)
- HTTP TRACE or OPTIONS methods enabled
- Self-XSS and issues exploitable only through Self-XSS
- Exploits that require physical access to a user's machine
- Non-sensitive (ie. non-session) cookies missing the Secure or HttpOnly flags
- Bugs that do not represent any security risk
- Submissions from former NordVPN employees within one year of their departure from NordVPN
- Issues found through automated testing
- "Scanner output" or scanner-generated reports
- SSL or ssh issues (weak ciphers/key-size/BEAST/CRIME)
- CSRF without proof of security impact
- Application or server error messages, stack traces
- All reports related to NordVPN Teams , NordLocker or NordPass services and infrastructure.
This program have been found on Hackerone on 2019-12-05.