dbcve.org
Parse ServerApplication · Parseplatform

CVE-2022-24901

HIGH · 7.5 CVSS v3.1 Published 2022-05-04
Fix available
A fix is available. Upgrade to 4.10.10 / 5.2.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Improper validation of the Apple certificate URL in the Apple Game Center authentication adapter allows attackers to bypass authentication, making the server vulnerable to DoS attacks. The vulnerability has been fixed by improving the URL validation and adding additional checks of the resource the URL points to before downloading it.

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 · moderate confidence

The Apple Game Center authentication adapter fails to properly validate Apple certificate URLs, allowing attackers to manipulate the URL to bypass authentication mechanisms. Additionally, the lack of validation on the resource the URL points to before downloading enables potential DoS attacks by forcing the server to download malicious or excessively large resources.

MitigationUpgrade or patch the Apple Game Center authentication adapter to a version that includes proper URL validation and resource verification before downloading certificates. Implement allowlist validation for URLs and add size/content-type checks on downloaded resources.

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
Parse ServerApplication
Affected:< 4.10.10>= 5.0.0, < 5.2.1

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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Parse Server installation and version
    Locate your Parse Server installation and determine the installed version using your package manager (e.g., npm list parse-server) or by checking your package.json dependencies
    Affected if The installed version is less than 4.10.10, or greater than or equal to 5.0.0 but less than 5.2.1
  2. Compare version against affected ranges
    Check your identified version against the affected ranges: versions < 4.10.10 OR >= 5.0.0 AND < 5.2.1
    Affected if The version falls within either < 4.10.10 or >= 5.0.0 but < 5.2.1
  3. Determine if Apple Game Center authentication is configured
    Examine your Parse Server configuration (config.json, environment variables, or server startup code) for the Apple Game Center authentication adapter (authData configuration with 'gameCenter' provider)
    Affected if Apple Game Center authentication is enabled in your Parse Server configuration

You are affected if your Parse Server version is in the vulnerable range AND Apple Game Center authentication is actively configured and used in your environment.

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 4.10.10 / 5.2.1 or later
Fixed in 4.10.105.2.1
Interim mitigation

Upgrade or patch the Apple Game Center authentication adapter to a version that includes proper URL validation and resource verification before downloading certificates. Implement allowlist validation for URLs and add size/content-type checks on downloaded resources.

Recommended fix High confidence

Parse Server 4.10.10 or 5.2.1

  1. 1. Back up your Parse Server database and configuration files
  2. 2. Check your current Parse Server version by running `parse-server --version` or checking package.json
  3. 3. If running version < 4.10.10: Run `npm install [email protected]` to upgrade to the fixed version
  4. 4. If running version >= 5.0.0 and < 5.2.1: Run `npm install [email protected]` to upgrade to the fixed version
  5. 5. Review the changelog for any configuration changes needed between your current version and the target version
  6. 6. Test the Apple Game Center authentication flow in a staging environment before deploying to production
  7. 7. Deploy the updated version to production and verify authentication works correctly
Caveat Review breaking changes in Parse Server 5.x releases if upgrading from 4.x; ensure Apple Game Center adapter configuration is properly set

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

Fix this in Parse Server 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-2022-24901 — 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-2022-24901 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