GHSA-mjcr-rqjg-rhg3

    Dashboard / Vulnerabilities / GHSA-mjcr-rqjg-rhg3

    GHSA-mjcr-rqjg-rhg3

    Published: 24 Nov 2020Last Modified: 21 Mar 2022

    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](https://indieauth.spec.indieweb.org/#differing-user-profile-urls-li-1) in the IndieAuth specification. ### For more information If you have any questions or comments about this advisory: * Open an issue in [simonw/datasette-indieauth](https://github.com/simonw/datasette-indieauth/issues)

    Affected packages

    Package

    Name: datasette-indieauth

    Purl: pkg:pypi/datasette-indieauth

    Affected ranges

    Type: ECOSYSTEM

    Events:

    Introduced- 1.0
    Fixed -1.1

    Affected versions

    1.0

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    GHSA-mjcr-rqjg-rhg3 | CVE-DB