GHSA-mjcr-rqjg-rhg3

Source

https://github.com/advisories/GHSA-mjcr-rqjg-rhg3

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/11/GHSA-mjcr-rqjg-rhg3/GHSA-mjcr-rqjg-rhg3.json

JSON Data

https://api.test.osv.dev/v1/vulns/GHSA-mjcr-rqjg-rhg3

Published

2020-11-24T21:21:04Z

Modified

2022-03-21T20:04:49Z

Summary

Implementation trusts the "me" field returned by the authorization server without verifying it

Details

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

Database specific

{
    "nvd_published_at": null,
    "cwe_ids": [
        "CWE-290"
    ],
    "severity": "CRITICAL",
    "github_reviewed": true,
    "github_reviewed_at": "2020-11-24T21:20:38Z"
}

References

Affected packages

PyPI / datasette-indieauth

Package

Name: datasette-indieauth; View open source insights on deps.dev
Purl: pkg:pypi/datasette-indieauth

Affected ranges

Type: ECOSYSTEM
Events: Introduced

1.0

Fixed

1.1

Affected versions

1.*

1.0