How severe is GHSA-mjcr-rqjg-rhg3?

No CVSS score has been assigned to GHSA-mjcr-rqjg-rhg3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mjcr-rqjg-rhg3?

GHSA-mjcr-rqjg-rhg3 affects the following packages: datasette-indieauth (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-mjcr-rqjg-rhg3?

Update datasette-indieauth to 1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mjcr-rqjg-rhg3 is resolved across your whole dependency graph.

How do I detect GHSA-mjcr-rqjg-rhg3 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datasette-indieauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-mjcr-rqjg-rhg3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-mjcr-rqjg-rhg3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mjcr-rqjg-rhg3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-mjcr-rqjg-rhg3 published, and has it been updated?

GHSA-mjcr-rqjg-rhg3 was published on November 24, 2020 and was last updated on March 21, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

Implementation trusts the "me" field returned by the authorization server without verifying itGHSA-mjcr-rqjg-rhg3

Fix: simonw/datasette-indieauth@376c880

GHSA-mjcr-rqjg-rhg3 is a security vulnerability in datasette-indieauth. A fix is available for datasette-indieauth — see the affected versions and patch details below.

Published

Nov 24, 2020

Updated

Mar 21, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 21, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍datasette-indieauth

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`datasette-indieauth`	≥ 1.0&&< 1.1	1.1`pip install --upgrade 'datasette-indieauth==1.1'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datasette-indieauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update datasette-indieauth to 1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mjcr-rqjg-rhg3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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](https://indieauth.spec.indieweb.org/#differing-user-profile-urls-li-1) in the IndieAuth specification. ### For more information If you have

O3 Security · Impact-Aware SCA

Is GHSA-mjcr-rqjg-rhg3 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works