← Back to the homepage

Security

Security Advisories

Report a vulnerability to us here — and read how we handle it: the fix first, then the publication.

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
E-mail
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

What you can expect from us

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

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.

Go to the advisory list →

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

Contact for questions: support.powerfolder.com · security@powerfolder.com · dal33t GmbH, Rheinpromenade 4a, 40789 Monheim am Rhein, Germany · Imprint