More than 45 vulnerabilities found and reported in coordinated disclosure.
We examine large open-source systems, report findings through the projects' official security processes and apply this knowledge to every piece of software we build or review.
1Published vulnerabilities
All published advisories. Further reports appear only once the respective fix is available.
2How a report proceeds
We publish nothing before the operators of a system have a fix.
- 2.1
Finding
Analysis on our own test system, never on third-party production instances.
- 2.2
Report
Confidentially via the project's security tracker, with reproduction steps and a proposed fix.
- 2.3
Fix
The project fixes the vulnerability and ships updates. On request, we verify the patch.
- 2.4
Publication
Only then are the CVE and details published, by the project and here in the list.
3What this means for your project
We check for the bug classes from our findings in every project we build or audit.
$ review src/ [*] Permission check per endpoint [*] Inputs and outputs [*] File and database access [*] Sessions, CSRF, redirects [+] Findings with severity and proposed fix [✓] Re-test after the fix
For third-party code, we offer this as a separate security audit: pentest, code audit or both.
4 / Contact
Should someone review your application?
Describe your project in three short steps. We usually reply within one working day.