GHSA-mjcr-rqjg-rhg3
Implementation trusts the "me" field returned by the authorization server without verifying it
GHSA-mjcr-rqjg-rhg3 is a vulnerability with no CVSS score yet in datasette-indieauth, published November 24, 2020. No source lists public exploit code. Fixed in datasette-indieauth 1.1.
- Severity
- UnratedNo CVSS score yet
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
1.1datasette-indieauth +1 more
Description
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 packages
| Package | Affected | Fixed |
|---|---|---|
datasette-indieauthPyPI | 1.0 to 1.0 | 1.1 |
datasette-indieauthPyPI | 1.0 up to 1.1 | 1.1 |
What each source reports
GitHub AdvisoriesNo score
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
- Record
GHSA-mjcr-rqjg-rhg3- Weakness
- CWE-290
- Updated
- 2026-11-02
OSVNo score
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
- Record
GHSA-mjcr-rqjg-rhg3- Weakness
- CWE-290
- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.