|
| 1 | +# Security Policy |
| 2 | + |
| 3 | +## Supported versions |
| 4 | + |
| 5 | +crudauth is pre-1.0. During this phase only the latest release receives security fixes. |
| 6 | +Always run the latest version. |
| 7 | + |
| 8 | +| Version | Supported | |
| 9 | +| -------------- | ------------- | |
| 10 | +| Latest release | Yes | |
| 11 | +| Older releases | No | |
| 12 | + |
| 13 | +## Reporting a vulnerability |
| 14 | + |
| 15 | +Please report security issues privately. Do not open a public issue for a vulnerability. |
| 16 | + |
| 17 | +Use either channel: |
| 18 | + |
| 19 | +- Email: **igor@benav.io** |
| 20 | +- GitHub Security Advisory: https://github.com/benavlabs/crudauth/security/advisories/new |
| 21 | + |
| 22 | +Include whatever you have: a description, steps to reproduce, the impact, the affected |
| 23 | +version, and a suggested fix if you have one. |
| 24 | + |
| 25 | +## What to expect |
| 26 | + |
| 27 | +- Acknowledgment within 48 hours. |
| 28 | +- A status update within a week. |
| 29 | +- A fix timeline based on severity, critical issues first. |
| 30 | +- Coordinated disclosure once a fix is released, with credit if you want it. |
| 31 | + |
| 32 | +## Scope |
| 33 | + |
| 34 | +crudauth is an authentication library, so its security behavior is the product. Reports |
| 35 | +about the auth surface are especially welcome: |
| 36 | + |
| 37 | +- session and CSRF handling |
| 38 | +- bearer-token signing, scope handling, and revocation |
| 39 | +- login lockout and rate limiting |
| 40 | +- OAuth `state` handling and redirect safety |
| 41 | +- password storage and verification |
| 42 | +- registration field gating (mass-assignment) |
| 43 | +- timing and user-enumeration properties of the login path |
| 44 | + |
| 45 | +Some properties are documented as irreducible by design (for example, a holder of a correct |
| 46 | +password can still infer that an account is disabled). If you are unsure whether something |
| 47 | +counts, report it anyway. |
0 commit comments