Port of Rotterdam
By Port of Rotterdam Authority Vulnerability disclosure program on Self-hosted portofrotterdam.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 0
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- 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.
This program does not pay cash rewards.
- 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
-
Full
If you have followed the instructions above, we will not take any legal action against you concerning the report.
- Hall of fame
-
Yes
Responsible disclosure hall of fame
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
0 assets you may test.
Self-hosted does not list the scope of this program publicly. Check its policy.
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Port of Rotterdam's policy. "We" in these lines means the program, not this site.
While testing
-
Report the vulnerability as quickly as is reasonably possible, to minimise the risk of hostile actors finding it and taking advantage of it.
-
Report in a manner that safeguards the confidentiality of the report so that others do not gain access to the information.
-
Provide sufficient information to reproduce the problem, so we will be able to resolve it.
-
Reveal the vulnerability or problem to others until it is resolved.
-
Build your own backdoor in an information system with the intention of then using it to demonstrate the vulnerability, because doing so can cause additional damage and create unnecessary security risks.
-
Utilise a vulnerability further than necessary to establish its existence.
-
Copy, modify or delete data on the system. An alternative for doing so is making a directory listing of the system.
-
Make changes to the system.
-
Repeatedly gain access to the system or sharing access with others.
-
Use brute force attacks, attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties to gain access to the system.
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 5 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.