← Back

Scratchoauth2 Project

scratchoauth2_project

4 CVEs • 1 product

Products (1)

Click to collapse
Toggle
Scratchoauth2
scratchoauth2
4 CVEs

CVEs (4)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
CVE-2021-46251
1Scratchoauth2 Project
1Scratchoauth2
Nov 21, 2024
Feb 15, 2022
N/A· v4
6.1 MEDIUM· v3
4.3 MEDIUM· v2
A reflected cross-site scripting (XSS) in ScratchOAuth2 before commit 1603f04e44ef67dde6ccffe866d2dca16defb293 allows attackers to execute arbitrary web scripts or HTML via a crafted POST request.
CVE-2021-46250
1Scratchoauth2 Project
1Scratchoauth2
Nov 21, 2024
Feb 15, 2022
N/A· v4
10.0 CRITICAL· v3
7.5 HIGH· v2
An issue in SOA2Login::commented of ScratchOAuth2 before commit a91879bd58fa83b09283c0708a1864cdf067c64a allows attackers to authenticate as other users on downstream components that rely on ScratchOAuth2.
CVE-2021-46249
1Scratchoauth2 Project
1Scratchoauth2
Nov 21, 2024
Feb 15, 2022
N/A· v4
6.5 MEDIUM· v3
4.0 MEDIUM· v2
An authorization bypass exploited by a user-controlled key in SpecificApps REST API in ScratchOAuth2 before commit d856dc704b2504cd3b92cf089fdd366dd40775d6 allows app owners to set flags that indicate whether an app is v...Show more
An authorization bypass exploited by a user-controlled key in SpecificApps REST API in ScratchOAuth2 before commit d856dc704b2504cd3b92cf089fdd366dd40775d6 allows app owners to set flags that indicate whether an app is verified on their own apps.Show less
CVE-2021-29437
1Scratchoauth2 Project
1Scratchoauth2
Nov 21, 2024
Apr 13, 2021
N/A· v4
6.8 MEDIUM· v3
4.0 MEDIUM· v2
ScratchOAuth2 is an Oauth implementation for Scratch. Any ScratchOAuth2-related data normally accessible and modifiable by a user can be read and modified by a third party. 1. Scratch user visits 3rd party site. 2. 3rd p...Show more
ScratchOAuth2 is an Oauth implementation for Scratch. Any ScratchOAuth2-related data normally accessible and modifiable by a user can be read and modified by a third party. 1. Scratch user visits 3rd party site. 2. 3rd party site asks user for Scratch username. 3. 3rd party site pretends to be user and gets login code from ScratchOAuth2. 4. 3rd party site gives code to user and instructs them to post it on their profile. 5. User posts code on their profile, not knowing it is a ScratchOAuth2 login code. 6. 3rd party site completes login with ScratchOAuth2. 7. 3rd party site has full access to anything the user could do if they directly logged in. See referenced GitHub security advisory for patch notes and workarounds.Show less