1. How we handle security
PowerFolder is developed and operated by dal33t GmbH in Germany. Security is not a finished project for us but part of every release: we review our interfaces, keep third-party libraries current, and assess reported vulnerabilities through a defined process.
We follow the principle of coordinated disclosure. Anyone who reports a vulnerability to us receives a reply, an assessment and a schedule. We publish an advisory as soon as an update or a dependable mitigation is available — and also when no patch exists yet, where operators can protect themselves by other means or where the risk calls for action. In that case we describe the workaround and say plainly that the final fix is still pending.
Customers under a maintenance agreement are informed about vulnerabilities and security incidents affecting our software within 72 hours of our becoming aware of them — whether or not an update is available at that point.
2. Reporting a vulnerability
Please report vulnerabilities through our support portal. The connection is encrypted, your report goes straight into our ticket system and receives a reference number under which you can follow its progress at any time. It is the secure route and the fastest one — a form, not a mailbox someone can overlook.
- Portal
- support.powerfolder.com — please set a high priority so the report is recognised as a security matter straight away
- security@powerfolder.com — if you would rather not use the portal. E-mail is not encrypted end to end in transit, so send a short note without technical detail first.
- Policy
- security.txt per RFC 9116
- Languages
- German, English
What your report should contain
- the affected product and version (server, client, my.powerfolder.com)
- a description of the vulnerability and its possible impact
- steps to reproduce it, ideally with requests, log excerpts or screenshots
- whether the issue is already known or published elsewhere, and whether a deadline applies
- how you would like to be named, if you want to be credited
What you can expect from us
- Step 1Acknowledgement within 2 working days. From a person, not an auto-responder.
- Step 2Initial assessment within 10 working days. We tell you whether we could reproduce the report, how we rate it and what happens next.
- Step 3Status updates at least every 14 days while the case is open.
- Step 4Publication of an advisory, as a rule at the same time as the update. We agree the timing with you, and credit you only with your consent.
Safe harbour
If you look for vulnerabilities in good faith and report them to us, you have nothing to fear from us legally. We regard such research as authorised and will not pursue it under civil or criminal law as long as you
- use only your own accounts and your own data, and neither access, alter, copy nor store anyone else's data,
- do not impair the availability or integrity of the services — no denial of service, no load testing, no spam,
- take no more access than is needed to demonstrate the vulnerability, and do not maintain access once obtained,
- report the vulnerability to us without delay and allow a reasonable period for a fix before publishing — as a rule 90 days.
Should third parties take legal action over such research, we will state that it was carried out with our consent. This promise cannot release us from obligations towards third parties: where someone else's infrastructure is involved, their policy applies.
3. Published advisories
We maintain the list of security advisories in our wiki, alongside the release notes. For every advisory it states which versions are affected, how we rate it, what helps without the update, and in which version it is fixed. The page is reachable without a login.
Every advisory receives a permanent identifier of the form PF-SA-YYYY-NNN and
remains available at that address. Where a CVE identifier has been assigned, we list it as
well; ratings follow CVSS v3.1. Each advisory states the summary, the affected versions, the
impact, our rating, the mitigation without an update, the fixed version and the timeline.
The corresponding downloads and their SHA-256 checksums are in the Server Release Notes and on our download page.
4. Supported versions
We provide security updates for the current release lines of PowerFolder Server. Which lines those are, and when a line runs out, is stated in the Server Release Notes, where we keep that information up to date.
The end of support for a line is announced at least six months in advance, in the release notes and by e-mail to the registered administrative contacts.
5. How we notify you
- E-mail to the registered administrative contacts. Every organisation running its own server registers a technical contact with us. This lets us reach operators directly, outside of a release as well.
- The advisory list in the wiki. Every advisory appears there, permanently and without a login.
- News on this website. Advisories of wider interest are also published under News and in the newsletter.
Contact for questions: support.powerfolder.com · security@powerfolder.com · dal33t GmbH, Rheinpromenade 4a, 40789 Monheim am Rhein, Germany · Imprint