Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

RIPE NCC

Bug bounty on Intigriti ripe.net

Accepting reports Full safe harbor
Go to program
Top reward
€2,000
Top severity paid
Critical
Assets in scope
10
Public CVEs
3
Last change

At a glance

What to know before you start testing.

Pays up to €2,000
for critical bugs.
Report on Intigriti
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
No public write-ups
Keep findings private.

Rewards

What Intigriti lists as the payout for each severity.

Severity Reward
Critical €2,000 from €200
High €700 from €100
Medium €250 from €50

Scope

10 assets you may test, 13 excluded.

Web 3

  • Assets owned by RIPE NCC
  • https://access.ripe.net
  • lirportal.ripe.net

Networks 1

  • 193.0.0.0/19 and 2001:67c:2e8::/48

Wildcard domains 1

  • *.ripe.net

Products and areas 5

  • https://github.com/RIPE-NCC/rpki-commons
  • https://github.com/RIPE-NCC/rpki-core
  • https://github.com/RIPE-NCC/rpki-monitoring
  • https://github.com/RIPE-NCC/rpki-ta-0
  • https://github.com/RIPE-NCC/whois
Out of scope (13)
  • https://github.com/RIPE-NCC/rpki-publication-server
  • https://github.com/RIPE-NCC/rsyncit
  • ripe[1-100].ripe.net
  • 193.0.0.160/27
  • 2001:67c:2e8:3::/64
  • https://exams.ripe.net
  • https://labs.ripe.net
  • RIPE Meeting network (2001:67c:64::/48 and 193.0.24.0/21)
  • *.anchors.atlas.ripe.net
  • any *.ripe.net host that is located outside of the in-scope ip ranges
  • *aso.ripe.net
  • *nro.ripe.net
  • *.probes.atlas.ripe.net

Rules

What the policy asks of you, and the bug types it won't reward, quoted from RIPE NCC (via Intigriti)'s policy. "We" in these lines means the program, not this site.

While testing

  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
  • While you test our assets, we ask you to adjust your scanners to stay below the limit of req/sec mentioned at the bottom of this page.
  • please don’t forget to use your @intigriti.me address

Not accepted

  • API key disclosure without proven business impact
  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that cannot be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking without proven impact/unrealistic user interaction
  • CSV Injection
  • Sessions not being invalidated (logout, enabling 2FA, etc.)
  • Tokens leaked to third parties
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection without being able to modify the HTML
  • Username/email enumeration
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing/Version disclosure

Summarised with AI from the program policy on Intigriti, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 30 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.

  1. Scope added

    https://access.ripe.net

  2. Scope added

    https://exams.ripe.net (out of scope)

  3. Scope added

    *nro.ripe.net (out of scope)

  4. Scope added

    ripe[1-100].ripe.net (out of scope)

  5. Scope removed

    *aso*ripe.net (out of scope)

  6. Scope removed

    *nro*ripe.net (out of scope)

  7. Scope added

    *aso.ripe.net (out of scope)

  8. Scope removed

    Assets owned by RIPE NCC

  9. Scope removed

    *.ripe.net

  10. Scope removed

    ripe(1to87).ripe.net (out of scope)

  11. Scope removed

    RIPE Meeting network (2001:67c:64::/48 and 193.0.24.0/21) (out of scope)

  12. Scope removed

    Any of the beta/dev environments (out of scope)

  13. Scope removed

    193.0.0.0/19 and 2001:67c:2e8::/48

  14. Scope removed

    2001:67c:2e8:3::/64 (out of scope)

  15. Scope removed

    lirportal.ripe.net

  16. Scope removed

    Any *.ripe.net host that is located outside of the in-scope IP ranges (out of scope)

  17. Scope removed

    https://github.com/RIPE-NCC/rpki-core

  18. Scope removed

    https://github.com/RIPE-NCC/rpki-monitoring

  19. Scope removed

    https://github.com/RIPE-NCC/rpki-ta-0

  20. Scope removed

    *.anchors.atlas.ripe.net (out of scope)

  21. Scope removed

    https://github.com/RIPE-NCC/rsyncit

  22. Scope removed

    *.probes.atlas.ripe.net (out of scope)

  23. Scope removed

    https://github.com/RIPE-NCC/whois

  24. Scope removed

    https://github.com/RIPE-NCC/rpki-publication-server

  25. Scope removed

    193.0.0.160/27 (out of scope)

  26. Scope removed

    193.0.0.0/19 and 2001:67c:2e8::/48

  27. Scope removed

    193.0.0.0/19 and 2001:67c:2e8::/48

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2020-16162 High 7.5 30 Jul 2020
CVE-2020-16163 Critical 9.1 30 Jul 2020
CVE-2020-16164 High 7.4 30 Jul 2020

Original policy

Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Description

We're an independent, not-for-profit membership organization that supports the infrastructure of the Internet through technical coordination in our service region. Our most prominent activity is to act as the Regional Internet Registry (RIR) providing global Internet resources and related services (IPv4, IPv6 and AS Number resources) to members in our service region.

Rules of engagement

By participating in this program, you agree to:

  • Respect the Community Code of Conduct
  • Respect the Intigriti Terms and Conditions
  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Validation times We will validate all submissions within the below timelines, once your submission has been verified by Intigriti. Submissions validated outside of this may be awarded a €25 bonus.

Vulnerability Severity Time to validate
Exceptional 2 Working days
Critical 2 Working days
High 5 Working days
Medium 15 Working days
Low 15 Working days

This remains at the discretion of the RIPE NCC to award.

Check our fix We offer up to €50 bonus to verify a resolved issue for us (when requested). This remains at the discretion of RIPE NCC to award.

In scope

Introduction We are happy to announce our bug bounty program! We've done our best to clean most of our known issues and now would like to request your help to spot the ones we missed!

Limits While you test our assets, we ask you to adjust your scanners to stay below the limit of req/sec mentioned at the bottom of this page. To avoid that your submission gets rejected as out-of-scope, make yourself familiar with the asset scope above.

Feedback Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback to [email protected]

Updates We are continuously going to update our program details, follow it to get notified on recent changes.

Out of scope

Known Issues (date last updated: 14/06/2022)

  • RIPE NCC Access: session invalidation after logout, rate limiting issues, weak password policy - we are working on a fix right now for some of these. Others will be fixed when the new SSO (RIPE NCC Access) platform is implemented later this year.
  • Hyperlink injection when registering a new account and sending password requests
  • labs.ripe.net IDOR's
  • Blind XSS on some forms at ripe.net

access.ripe.net

Out of scope:

  • Session invalidation issues
  • Password policy - best practices
  • Rate limiting issues (password reset request, etc)

DNS

DNS zone transfers (XFER request) are excluded from the scope

Abuse

  • Malicious activity originating from IP address space in the RIPE region, but not used by the RIPE NCC. Being a Regional Internet Registry we frequently receive abuse reports for Internet resources (IP addresses and AS numbers) for which we are not responsible. If you’re facing this issue, please check this page to see which organisation you should contact: https://www.ripe.net/support/abuse

Public data repositories

The RIPE NCC has a number of public data repositories. These do not contain sensitive data and everything in there is really public - so no need to report them. The services include:

  • ftp.ripe.net
  • ris.ripe.net
  • rpki.ripe.net
  • sg-pub.ripe.net
  • ...

Application

  • API key disclosure without proven business impact
  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that cannot be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking without proven impact/unrealistic user interaction
  • CSV Injection
  • Sessions not being invalidated (logout, enabling 2FA, etc.)
  • Tokens leaked to third parties
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection without being able to modify the HTML
  • Username/email enumeration
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing/Version disclosure
  • Not stripping metadata of files
  • Same-site scripting
  • Subdomain takeover without taking over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file
  • Blind SSRF without proven business impact (pingbacks are not sufficient)
  • Disclosed/misconfigured Google Maps API keys
  • Host header injection without proven business impact
  • Open redirect - Unless an impact proven
  • Finding the IP Address of our websites behind WAF's without any working exploit
  • Image upload or retrieval from labs.ripe.net

General

  • In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
  • Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks
  • Vulnerabilities that only work on software that no longer receive security updates
  • Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
  • Recently discovered zero-day vulnerabilities found in in-scope assets within three weeks after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
  • Reports that state that software is out of date/vulnerable without a proof-of-concept

Severity

This program follows Intigriti's triage standards

Though we are following the Intigriti's CVSS standart, business impacts may be different than the actual score. Final decision will be made after our assesment and set accordingly.

FAQ

Where can we get credentials for the app?

You can self-register on the application but please don’t forget to use your @intigriti.me address.

I've found a bug which considered as out-of-scope but I can chain it to exploit in-scope targets, what should I do?

If you have doubts about the bug you've found, you can contact Intigriti Support, so we can discuss together and let you know if you should submit the bug via here or not.

Who can submit bugs to our program?

RIPE NCC Bug Bounty Programme can not be used by RIPE NCC Employees or any external consultants working for RIPE NCC.