Reporting a vulnerability
If you think you have found a security problem in ianua, please tell us privately first. Do not open a public issue, pull request or discussion about it. That gives us time to fix it before anyone can use it against the people running ianua.
How to report
Section titled “How to report”Send your report to [security contact, to be added].
If you can, encrypt it with [key, to be added].
What to include
Section titled “What to include”The more of this you can give us, the faster we can fix it:
- What the problem is, in a sentence or two.
- Where it is: the part of ianua (the dashboard, the API, the gateway, an SDK) and the version or commit.
- How to make it happen: the steps, a request, or a small script.
- What someone could do with it: for example, read another tenant’s users, or sign in without a password.
- How you would like to be credited, if at all.
You don’t need a full write-up or a working exploit. A clear description of what you saw is enough to start.
What happens next
Section titled “What happens next”- We confirm we got it within [time, to be added].
- We check it and tell you whether we can reproduce it, usually within [time, to be added].
- We fix it and agree a date with you to publish the fix and the advisory.
- We credit you in the advisory, unless you would rather not be named.
We will keep you up to date while we work on it.
What counts
Section titled “What counts”Anything that lets someone get past one of the promises on the Security model page is in scope. For example:
- getting into an app behind the gateway without being allowed,
- seeing or changing another tenant’s data,
- signing in as someone else,
- getting a secret, key or token out of the platform,
- changing or removing audit records without it showing.
These are not security problems on their own:
- findings that need a database superuser or the platform’s own keys (see what ianua does not protect you from, on the Security model page),
- an app that can be reached without going through the gateway,
- problems in a setup running with
APP_ENV=development, - reports from automated scanners with no sign that the problem can actually be used.
Testing safely
Section titled “Testing safely”Test only on an installation you run yourself. Please don’t test against installations other people run, don’t read or change data that isn’t yours, and stop as soon as you have shown the problem.