- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 11
- Public CVEs
- 3
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 3 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
Bounties for valid reports
- Response
-
Within 3 days
We will strive to respond to your report within three business days with our evaluation of the report and an expected resolution date
- Safe harbor
-
Partial
The RIPE NCC reserves the right to initiate legal action against researchers for penetrating or attempting to penetrate our systems if they do not adhere to this policy.
- Hall of fame
-
Yes
After your vulnerability report is verified, you may be eligible for a reward and there is a chance your name will appear on the Intigriti leaderboard .
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
11 assets you may test, 3 excluded.
Domains 6
- anchors.atlas.ripe.net
- data-store.ripe.net
- ftp.ripe.net
- probes.atlas.ripe.net
- ripe.net
- www-static.ripe.net
Wildcard domains 3
- *.anchors.atlas.ripe.net
- *.probes.atlas.ripe.net
- *.ripe.net
Networks 2
- 193.0.0.160/27
- 2001:67c:2e8:3::/64
Out of scope (3)
- Any *.ripe.net host located outside of the in-scope IP ranges
- Public directories (many of them are supposed to be public)
- RIPE Meeting network (2001:67c:64::/48 and 193.0.24.0/21)
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Ripe NCC's policy. "We" in these lines means the program, not this site.
While testing
-
Performing actions that may negatively affect the RIPE NCC or its users (e.g. any form of Denial of Service attacks)
-
Accessing, or attempting to access, data or information that does not belong to the researcher for purposes other than performing the security test
-
Destroying or corrupting, or attempting to destroy or corrupt, data or information that does not belong to the researcher
-
Conducting any kind of physical or electronic attack on RIPE NCC personnel, property or data centres
-
Using social engineering to target any RIPE NCC employee
-
Violating any laws or breaching any agreements in order to discover vulnerabilities
-
Please do not share the issue with others until it has been resolved
-
Please do not publish anything about the resolved issue unless this has been discussed with us
-
Please delete all confidential information obtained through the vulnerability as soon as possible after reporting it, but always after consulting us to make sure that we can reproduce the issue
Not accepted
-
Missing, or not 'properly' configured SPF, DKIM or DMARC records
-
The presence of public services such as robots.txt or FTP (e.g. ftp.ripe.net )
-
The availability of DNS zone transfers
-
Reports of old software versions without a working Proof of Concept of an exploit
-
Image upload or retrieval from labs.ripe.net
-
Malicious activity originating from an IP address space in the RIPE region, but not used by the RIPE NCC.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 6 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2020-16162 | An issue was discovered in RIPE NCC RPKI Validator 3.x through 3.1-2020.07.06.14.28. Missing validation checks on CRL presence or CRL staleness in the X509-based RPKI certificate-tree validation procedure allow remote attackers to bypass intended access restrictions by using revoked certificates. NOTE: there may be counterarguments related to backwards compatibility | High 7.5 | 30 Jul 2020 |
| CVE-2020-16163 | An issue was discovered in RIPE NCC RPKI Validator 3.x before 3.1-2020.07.06.14.28. RRDP fetches proceed even with a lack of validation of a TLS HTTPS endpoint. This allows remote attackers to bypass intended access restrictions, or to trigger denial of service to traffic directed to co-dependent routing systems. NOTE: third parties assert that the behavior is intentionally permitted by RFC 8182 | Critical 9.1 | 30 Jul 2020 |
| CVE-2020-16164 | An issue was discovered in RIPE NCC RPKI Validator 3.x through 3.1-2020.07.06.14.28. It allows remote attackers to bypass intended access restrictions or to cause a denial of service on dependent routing systems by strategically withholding RPKI Route Origin Authorisation ".roa" files or X509 Certificate Revocation List files from the RPKI relying party's view. NOTE: some third parties may regard | High 7.4 | 30 Jul 2020 |