GHSA-mjcr-rqjg-rhg3: Implementation trusts the "me" field returned by the authorization server without verifying it
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Fixed version: datasette-indieauth (PyPI) 1.1.
Low priority for now. Upgrade to datasette-indieauth (PyPI) 1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
### 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)
- Published
- Nov 24, 2020
- Updated
- Mar 21, 2022
- EPSS
- —
- CWE
- CWE-290
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| PyPI | datasette-indieauth | pkg:pypi/datasette-indieauth |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | datasette-indieauth | from 1.0 · before 1.1 | 1.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PyPI:datasette-indieauth | 1.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
CWE-290 · Authentication Bypass by SpoofingAttack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Web Services API Signature Forgery Leveraging Hash Function Extension WeaknessCAPEC-461High
- Signature SpoofCAPEC-473
- Signature Spoofing by MisrepresentationCAPEC-476likelihood: Low · High
- Session Credential Falsification through PredictionCAPEC-59likelihood: High · High
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- Masquerading: Invalid Code SignatureT1036.001
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls: Code SigningT1553.002
- Adversary-in-the-MiddleT1557
Change log (2)
- Fix✗ → ✓
- CVSS9.5 → —
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.