dbcve.org
Scratchoauth2Application · Scratchoauth2 Project

CVE-2021-46250

CRITICAL · 10.0 CVSS v3.1 Published 2022-02-15
Fix available
A fix is available. Upgrade to 2021-04-13 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue in SOA2Login::commented of ScratchOAuth2 before commit a91879bd58fa83b09283c0708a1864cdf067c64a allows attackers to authenticate as other users on downstream components that rely on ScratchOAuth2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

Authentication bypass vulnerability in ScratchOAuth2's SOA2Login::commented component that allows attackers to impersonate other users. The flaw enables unauthorized authentication as arbitrary users on downstream systems that depend on ScratchOAuth2 for user authentication.

MitigationUpgrade to the fixed version of ScratchOAuth2 (post-commit a91879bd58fa83b09283c0708a1864cdf067c64a) and audit downstream components relying on ScratchOAuth2 for authentication to confirm they are not vulnerable to user impersonation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Scratchoauth2Application
Affected:< 2021-04-13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ScratchOAuth2 is deployed in your environment
    Search your codebase, dependencies, or installed packages for references to the Scratchoauth2 or SOA2Login component. Review your project dependencies or gemfile/package-lock for the Scratchoauth2 library.
    Affected if Scratchoauth2 is found as a dependency or deployed component in your system
  2. Determine the installed version of ScratchOAuth2
    Check your dependency lock file, package manager records, or the library version metadata to identify which version of ScratchOAuth2 is currently in use. Compare the version or last commit date to April 13, 2021.
    Affected if The installed version predates April 13, 2021 or the specific fix commit a91879bd58fa83b09283c0708a1864cdf067c64a
  3. Check if the SOA2Login::commented component is in use
    Search your application code for any calls, routes, or references to the SOA2Login::commented component or commented method within the ScratchOAuth2 integration.
    Affected if The SOA2Login::commented component is actively used by your application
  4. Verify if downstream systems rely on ScratchOAuth2 for authentication
    Audit systems that integrate with ScratchOAuth2 to determine if they depend on it for user authentication or session management. Identify any services accepting authentication tokens or sessions from ScratchOAuth2.
    Affected if Downstream systems depend on ScratchOAuth2 for user authentication and are using a vulnerable version

Your environment is affected if ScratchOAuth2 version prior to April 13, 2021 is deployed AND the SOA2Login::commented component is in use AND downstream systems rely on it for authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2021-04-13 or later
Fixed in 2021-04-13
Vendor patch github.com →
Interim mitigation

Upgrade to the fixed version of ScratchOAuth2 (post-commit a91879bd58fa83b09283c0708a1864cdf067c64a) and audit downstream components relying on ScratchOAuth2 for authentication to confirm they are not vulnerable to user impersonation.

Recommended fix Moderate confidence

Any version/release after commit a91879bd58fa83b09283c0708a1864cdf067c64a (post-2021-04-13)

  1. 1. Identify the current version of ScratchOAuth2 being used in your deployment
  2. 2. Navigate to the GitHub repository: https://github.com/ScratchVerifier/ScratchOAuth2
  3. 3. Check the commit history for commit a91879bd58fa83b09283c0708a1864cdf067c64a
  4. 4. Upgrade to the version that includes this commit (any version after 2021-04-13)
  5. 5. Verify the upgrade by testing the authentication flow, specifically the SOA2Login::commented function
  6. 6. Ensure no unauthorized users can authenticate as other users

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Scratchoauth2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-46250 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-46250 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data