Rotterdam University of Applied Sciences (RUAS)
Bug bounty on Self-hosted rotterdamuas.com
- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 3
- Public CVEs
- 0
- 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 5 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
As a token of our gratitude for your assistance, we may offer a reward for every report of a security problem that was not yet known to us.
- Response
-
Within 5 days
We will respond to your report within 5 business days with our evaluation of the report and an expected resolution date.
- Safe harbor
-
Partial
If you adhere to the conditions below, we, RUAS, will not take any legal action against you. The Public Prosecution Service (OM) has the right to decide whether it will take action on it's own behalf.
- Hall of fame
-
Yes
In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise).
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
3 assets you may test, 5 excluded.
Domains 3
- hr.nl
- hro.nl
- rotterdamuas.com
Out of scope (5)
- 145.24.129.62
- 145.24.222.0/24
- octagon.hro.nl
- All websites hosted on 145.24.129.62 (octagon.hro.nl)
- Everything in the 145.24.222.0/24 network
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Rotterdam University of Applied Sciences (RUAS)'s policy. "We" in these lines means the program, not this site.
While testing
-
Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data.
-
Be extra careful with personal data.
-
Do not reveal the problem to others until it has been resolved.
-
Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties.
-
Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible.
Not accepted
-
HTTP 404 codes/pages or other HTTP non-200 codes/pages and Content Spoofing/Text Injection on these pages.
-
fingerprint version banner disclosure on common/public services.
-
disclosure of known public files or directories or non-sensitive information, (e.g. robots.txt).
-
clickjacking and issues only exploitable through clickjacking.
-
lack of Secure/HTTPOnly flags on non-sensitive Cookies.
-
OPTIONS HTTP method enabled.
-
anything related to HTTP security headers, e.g.:
-
Strict-Transport-Security.
-
X-Frame-Options.
-
X-XSS-Protection.
-
X-Content-Type-Options.
-
Content-Security-Policy.
-
SSL Configuration Issues:
-
SSL forward secrecy not enabled.
-
weak / insecure cipher suites.
-
SPF, DKIM, DMARC issues.
-
host header injection.
-
reporting older versions of any software without proof of concept or working exploit.
-
information leakage in metadata.
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.