CVE-2021-47987: Incorrect version tags linked to external repository
Impact A security incident caused a number of incorrect version tags to be pushed to the Parse Server repository. These version tags linked to a personal fork of a contributor who had write access to the repository. The code to which these tags linked has not been reviewed or approved by Parse Platform. Even though no releases were published with these incorrect versions, it was possible to define a Parse Server dependency that pointed to these version tags, for example if you defined this dependency: js "parse-server": "git@github.com:parse-community/parse-server.git#4.9.3"
We have since deleted the incorrect version tags, but they may still show up in your personal fork on GitHub or locally. We do not know when these tags have been pushed to the Parse Server repository, but we first became aware of this issue on July 21, 2021. We are not aware of any malicious code or concerns related to privacy, security or legality (e.g. proprietary code). However, it has been reported that some functionality does not work as expected and the introduction of security vulnerabilities cannot be ruled out.
You may be also affected if you used the Bitnami image for Parse Server. Bitnami picked up the incorrect version tag 4.9.3 and published a new Bitnami image for Parse Server. If you are using any of the affected versions, we urgently recommend to upgrade to version 4.10.0.
These are the incorrect tags: 4.0.0-beta1 4.0.0-beta2 4.0.0-beta3 4.0.0-beta4 4.0.0-beta5 4.0.0-beta6 4.0.10 4.0.11 4.0.12 4.0.13 4.0.14 4.0.3 4.0.4 4.0.6 4.0.7 4.0.8 4.0.9 4.6.0 4.6.0-beta 4.7.0 4.8.0 4.8.1 4.8.2 4.8.3 4.8.4 4.8.5 4.9.0 4.9.1 4.9.2 4.9.3
Patches Upgrade to version 4.10.0.
Workarounds Downgrade to version 4.5.2.
References n/a
Other sources
Parse Server before 4.10.0 was affected by a supply chain incident in which incorrect version tags were pushed to the official repository pointing to an unreviewed personal fork of a contributor with write access. No releases were published with these tags; a project was exposed only if it defined a git-based dependency referencing one of the affected tags (for example, parse-server#4.9.3). The code behind the tags was not reviewed or approved, and although no malicious code was identified, the introduction of security vulnerabilities could not be ruled out.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/parse-serverto a version that resolves this vulnerability.Fixed in 4.5.2 - Upgrade
Upgrade
npm/parse-serverto a version that resolves this vulnerability.Fixed in 4.10.0 - Upgrade
Upgrade
parse-serverto a version that resolves this vulnerability.Fixed in 4.10.0
Event History
Frequently Asked Questions
What is the severity of CVE-2021-47987?
CVE-2021-47987 has a high severity rating of 7.7.
How do I fix CVE-2021-47987?
To fix CVE-2021-47987, update your Parse Server to version 4.10.0 or later.
What are the risks associated with CVE-2021-47987?
CVE-2021-47987 allows for arbitrary code execution, potentially compromising the security of affected applications.
Which versions of Parse Server are affected by CVE-2021-47987?
CVE-2021-47987 affects all versions of Parse Server before 4.10.0.
Is there a known exploit for CVE-2021-47987?
There is no known exploit reported for CVE-2021-47987, but it poses a risk due to arbitrary code execution capabilities.