GHSA-MJCR-RQJG-RHG3
Vulnerability from github – Published: 2020-11-24 21:21 – Updated: 2022-03-21 20:04Impact
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": [
{
"package": {
"ecosystem": "PyPI",
"name": "datasette-indieauth"
},
"ranges": [
{
"events": [
{
"introduced": "1.0"
},
{
"fixed": "1.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0"
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-290"
],
"github_reviewed": true,
"github_reviewed_at": "2020-11-24T21:20:38Z",
"nvd_published_at": null,
"severity": "CRITICAL"
},
"details": "### Impact\n\nA 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.\n\n### Patches\n\nVersion 1.1 fixes this issue.\n\n### Workarounds\n\nThere is no workaround. Upgrade to 1.1 immediately.\n\n### References\n\n- [Security Considerations: Differing User Profile URLs](https://indieauth.spec.indieweb.org/#differing-user-profile-urls-li-1) in the IndieAuth specification.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [simonw/datasette-indieauth](https://github.com/simonw/datasette-indieauth/issues)",
"id": "GHSA-mjcr-rqjg-rhg3",
"modified": "2022-03-21T20:04:49Z",
"published": "2020-11-24T21:21:04Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/simonw/datasette-indieauth/security/advisories/GHSA-mjcr-rqjg-rhg3"
},
{
"type": "WEB",
"url": "https://github.com/simonw/datasette-indieauth/commit/376c8804c6b0811852049229a24336fe5eb6a439"
},
{
"type": "PACKAGE",
"url": "https://github.com/simonw/datasette-indieauth"
},
{
"type": "WEB",
"url": "https://pypi.org/project/datasette-indieauth"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Implementation trusts the \"me\" field returned by the authorization server without verifying it"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.