Responsible disclosure
Found a security problem in Dodona? Tell us at [email protected]. This page explains what we promise you, what we ask of you, and what Belgian law adds.
How to report
Send an email to [email protected], in English or Dutch, with:
- what you found and where (a URL, or the course or exercise);
- the steps to reproduce it;
- what you could see or change with it.
If you came across someone else's personal data, describe what kind of data it was. Don't send the data itself.
What we promise
- We confirm that we received your report within 2 working days.
- We keep you informed, and tell you when the problem is fixed.
- We treat your report and your name as confidential. See "Students" below for the one case where we tell a teacher who you are.
- We won't take legal action or file a complaint against you, as long as you follow the rules on this page.
- If you want, we thank you by name when we announce the fix.
If you follow the rules on this page, we consider your testing authorised. We won't treat it as a breach of the Acceptable Use Policy in our terms and conditions (section 4), and we won't block your account for it. If you break these rules, the terms apply as usual.
We don't pay rewards for reports.
What we ask of you
- Only your own data. Test with your own accounts. Don't read, change or delete anything that belongs to someone else, such as another student's submissions, a teacher's course, or grades.
- No graded work. Don't test in an exam, an evaluation or any other graded work. Reporting a problem doesn't make it acceptable to use it in a graded submission.
- Stop at proof. Do only what you need to show the problem exists. If you see someone else's data, or your code gets out of the sandbox that runs submissions, stop and report it. Don't look further, don't keep access, and don't touch other people's submissions.
- Report quickly, and keep it confidential. Report within 24 hours of finding the problem. Don't share it with anyone else except the Centre for Cybersecurity Belgium (see below), or make it public, until we've fixed it and agreed with you on what can be published.
- No attacks on availability or people. No denial of service or load testing, no spam, and no phishing or other social engineering of our team or our users.
Once you've reported, delete any data you got through the problem.
You're responsible for everything done on your behalf, including by scripts, scanners or AI agents. These rules apply to them too.
Students
Dodona is used in courses run by teachers and schools. That makes a few things different for students:
- Your school's rules still apply. This page covers what Dodona will and won't do. Your school or university may have its own rules about security testing, about how you use your school account, and about exams. Those rules still apply, and we can't waive them. If you're not sure, ask them.
- We don't decide your grades. Our promise not to take legal action says nothing about how your teacher grades your work.
- We don't tell your teacher you reported something. The exception: if your testing changed data in a course (a submission, a grade or an evaluation), we tell that course's teachers what happened and who did it.
- We inform affected teachers ourselves. If a problem exposed data in a course, we tell its teachers. You don't have to.
- Need a place to test? Students can't create their own course. Ask us at [email protected] and we'll set up a test course for you.
What's in scope
In scope:
- the Dodona website and its API on dodona.be;
- the sandbox that runs and judges submitted code.
Not in scope:
- an exercise whose tests accept a wrong solution: that's a problem in the exercise, so tell its author;
- services we use but don't run, such as the Microsoft, Google or Smartschool sign-in pages;
- reports from automated tools or AI that don't show a concrete problem you checked yourself.
Belgian law
Belgian law gives extra protection to people who report vulnerabilities, if they also report to the Centre for Cybersecurity Belgium (CCB) and meet strict conditions and deadlines. The CCB explains them on its website. Our promises above apply either way.