Rote 1.2.0 through 2.6.0 Account Takeover via OAuth Account Merge Endpoint
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Rabithua | Rote | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Rabithua | Rote |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.402% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rabithua
Rabithua rote |
|
| Vendors & Products |
Rabithua
Rabithua rote |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Rote 1.2.0 through 2.6.0 contains an authorization bypass in the OAuth bind/merge endpoint that allows authenticated users to merge any OAuth-bound account into their own. Attackers can submit a public existingUserId and GitHub or Apple user ID to take over notes, attachments, and API keys and delete the victim account. | |
| Title | Rote 1.2.0 through 2.6.0 Account Takeover via OAuth Account Merge Endpoint | |
| Weaknesses | CWE-639 | |
| References |
|
|
| Metrics |
cvssV3_1
|