CVE-2022-31083

Workarounds

None.

References

• https://github.com/parse-community/parse-server/security/advisories/GHSA-rh9j-f5f8-rvgc
• https://developer.apple.com/news/?id=stttq465
• https://github.com/parse-community/parse-server

More information

• For questions or comments about this vulnerability visit our community forum or community chat
• Report other vulnerabilities at report.parseplatform.org

The certificate in Apple Game Center auth adapter not validated. As a result, authentication could potentially be bypassed by making a fake certificate accessible via certain Apple domains and providing the URL to that certificate in an authData object.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2022-31083 has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.10.11, 5.2.2); upgrading removes the vulnerable code path.

Kodem intelligence

To prevent this, a new rootCertificateUrl property is introduced to the Parse Server Apple Game Center auth adapter which takes the URL to the root certificate of Apple's Game Center authentication certificate. If no value is set, the rootCertificateUrl property defaults to the URL of the current root certificate as of May 27, 2022.

Keep in mind that the root certificate can change at any time (expected to be announced by Apple) and that it is the developer's responsibility to keep the root certificate URL up-to-date when using the Parse Server Apple Game Center auth adapter.

1. What is CVE-2022-31083? CVE-2022-31083 is a high-severity improper authentication vulnerability in parse-server (npm), affecting versions < 4.10.11. It is fixed in 4.10.11, 5.2.2. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2022-31083? CVE-2022-31083 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of parse-server are affected by CVE-2022-31083? parse-server (npm) versions < 4.10.11 is affected.
4. Is there a fix for CVE-2022-31083? Yes. CVE-2022-31083 is fixed in 4.10.11, 5.2.2. Upgrade to this version or later.
5. Is CVE-2022-31083 exploitable, and should I be worried? Whether CVE-2022-31083 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31083 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31083?
   • Upgrade parse-server to 4.10.11 or later
   • Upgrade parse-server to 5.2.2 or later

Other vulnerabilities in parse-server