# CVE-2021-46249: Auth bypass in n/a

> Attackers can bypass authorization checks in the ScratchOAuth2 library to incorrectly mark their own applications as verified.

- **Severity:** Medium 6.5 (`CVSS:3.1/AC:L/AV:N/A:N/C:N/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v85q-g5fq-684c

## What is CVE-2021-46249?

CVE-2021-46249 is a medium-severity authentication bypass vulnerability in n/a, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2021-46249?

It affects 1 product.


Products: Scratchoauth2 Project Scratchoauth2.

## How do I fix CVE-2021-46249?

No fix has been published for CVE-2021-46249 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-46249 being exploited?

There is no known exploitation of CVE-2021-46249 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-46250](https://insights.sbomify.com/CVE-2021-46250/): Auth bypass in n/a (critical 10.0)
- [CVE-2021-29437](https://insights.sbomify.com/CVE-2021-29437/): Account compromise by man-in-the-middle attack (high 8.0)
- [CVE-2021-46251](https://insights.sbomify.com/CVE-2021-46251/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46249 and fix it if it is affected.

What it is: CVE-2021-46249 is a medium-severity authentication bypass vulnerability in n/a, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-46249 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-46249/ (Markdown: https://insights.sbomify.com/CVE-2021-46249/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-46249
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-46249
- OSV: https://osv.dev/vulnerability/CVE-2021-46249

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-46249/
Summaries are generated and may contain mistakes; the official description above is the record.