Participation and disclosure terms
Version: 2026-11-22
By participating in the SUNET Nextcloud security challenge, contestants agree to these terms.
Authorized scope
Testing is authorized only against these challenge instances and only during the published contest window:
stock.ctf.drive.test.sunet.sedrive.ctf.drive.test.sunet.sestock-fg.ctf.drive.test.sunet.sedrive-fg.ctf.drive.test.sunet.se
The submission service, cluster administration interfaces, node addresses, container registry, GitHub, identity providers, and all other SUNET systems are outside the authorized scope.
Contestants must not:
- Attack systems or accounts outside the authorized scope.
- Intentionally degrade availability or prevent others from participating.
- Destroy or alter another contestant's data.
- Establish persistence beyond what is necessary to demonstrate a finding.
- Retain or disclose credentials, personal data, private keys, or other sensitive data obtained during testing. Challenge flags may be sent privately to SUNET through the submission and reporting process but must not be disclosed elsewhere.
- Use a finding against any system outside this challenge.
Testing must stop when the contest closes or when an organizer requests it.
Coordinated disclosure
Every successful exploit and every credible security vulnerability found during the challenge is subject to coordinated disclosure.
SUNET is the disclosure coordinator for challenge findings. Contestants report findings to SUNET rather than contacting Nextcloud, application maintainers, or other affected projects independently. SUNET will triage the reports, consolidate duplicate findings where appropriate, contact the relevant upstream security team through a private channel, and coordinate remediation and publication.
SUNET cannot unilaterally determine or promise a publication date. The affected upstream project must have as much time as it needs to investigate, develop and validate fixes, and distribute them through its supported release process. A finding may remain private through several upstream release cycles. There is no automatic disclosure deadline.
Contestants must:
- Report the finding privately to the organizers through the reporting channel published on the challenge site.
- Allow SUNET to share the report with the maintainers or security contacts for the affected software.
- Keep technical details private until SUNET explicitly confirms that the affected upstream project is ready for publication and that the coordinated disclosure process permits it.
- Avoid opening a public issue, publishing proof-of-concept code, or discussing exploitable details publicly before that approval.
- Cooperate in good faith with reasonable requests for clarification, reproduction, or validation.
- Not contact an affected project about the finding unless SUNET asks them to do so or agrees on that communication in advance.
- Continue to respect the embargo after the challenge ends, regardless of how many upstream release cycles are required.
SUNET may include a contestant directly in upstream communication when useful and with the contestant's agreement. SUNET will seek to preserve the contestant's preferred name or alias when crediting a finding, subject to the affected project's disclosure process.
Required write-up
Contestants must provide a private write-up for every successful exploit. The write-up must be detailed enough to serve as the basis for a responsible security report to the affected software project.
At minimum, it must include:
- The affected component, version, and challenge instance.
- The challenge flag obtained through the exploit.
- The vulnerability class and likely root cause.
- Required access, configuration, and other preconditions.
- Reproducible steps or a minimal proof of concept.
- The resulting impact and privilege level.
- Relevant requests, responses, logs, or other evidence.
- Any known limitations or reliability considerations.
- Suggested mitigation or remediation, when known.
Reports must redact tokens, credentials, personal data, and unrelated secrets. A flag value by itself is not a sufficient write-up.
Contestants must submit their write-ups as soon as practical after the contest. Scores may be displayed immediately, but a contestant must provide the required write-ups and participate in coordinated disclosure to remain eligible for formal recognition.
Submission identity
The public scoreboard displays aliases only. Email addresses and submission tokens are private.
The token issued with the first accepted submission controls the registered alias. Contestants must not submit under another person's alias, share their token, or claim another contestant's work without permission and attribution.