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.

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.

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!

Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:
Program Feedback Link
Please note this form will be checked periodically and should not be used for submission or support queries.

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

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

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.

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.