Implementation trusts the "me" field returned by the authorization server without verifying it
Impact
A malicious user can sign in as a user with any IndieAuth identifier. This is because the implementation does not verify that the final "me" URL value returned by the authorization server belongs to the same domain as the initial value entered by the user.
Patches
Version 1.1 fixes this issue.
Workarounds
There is no workaround. Upgrade to 1.1 immediately.
References
- Security Considerations: Differing User Profile URLs in the IndieAuth specification.
For more information
If you have any questions or comments about this advisory:
- Open an issue in simonw/datasette-indieauth
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | datasette-indieauth | >= 1.0, < 1.1 | 1.1 |
References
- Weakness (CWE)
CWE-290- Platform
- Python (PyPI)
- Package
datasette-indieauth- Disclosed
- 24.11.2020
- Updated
- 11.10.2026 11:18
Sources and licenses
OSV / GitHub Advisory Database - GHSA-mjcr-rqjg-rhg3 - CC BY 4.0
Vulnerability history: datasette-indieauth
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.