CVSS: 9.8EPSS: 0%CPEs: 2EXPL: 0CVE-2022-41878 – Parse Server Prototype pollution and Injection via Cloud Code Webhooks or Cloud Code Triggers
https://notcve.org/view.php?id=CVE-2022-41878
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In versions prior to 5.3.2 or 4.10.19, keywords that are specified in the Parse Server option `requestKeywordDenylist` can be injected via Cloud Code Webhooks or Triggers. This will result in the keyword being saved to the database, bypassing the `requestKeywordDenylist` option. This issue is fixed in versions 4.10.19, and 5.3.2. If upgrade is not possible, the following Workarounds may be applied: Configure your firewall to only allow trusted servers to make request to the Parse Server Cloud Code Webhooks API, or block the API completely if you are not using the feature. • https://github.com/parse-community/parse-server/security/advisories/GHSA-xprv-wvh7-qqqx • CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') •
CVSS: 9.8EPSS: 0%CPEs: 2EXPL: 0CVE-2022-39396 – Parse Server vulnerable to Remote Code Execution via prototype pollution in MongoDB BSON parser
https://notcve.org/view.php?id=CVE-2022-39396
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Versions prior to 4.10.18, and prior to 5.3.1 on the 5.X branch, are vulnerable to Remote Code Execution via prototype pollution. An attacker can use this prototype pollution sink to trigger a remote code execution through the MongoDB BSON parser. This issue is patched in version 5.3.1 and in 4.10.18. There are no known workarounds. • https://github.com/parse-community/parse-server/security/advisories/GHSA-prm5-8g2m-24gg • CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') •
CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-39313 – Parse Server crashes when receiving file download request with invalid byte range
https://notcve.org/view.php?id=CVE-2022-39313
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Versions prior to 4.10.17, and prior to 5.2.8 on the 5.x branch, crash when a file download request is received with an invalid byte range, resulting in a Denial of Service. This issue has been patched in versions 4.10.17, and 5.2.8. There are no known workarounds. Parse Server es un backend de código abierto que puede desplegarse en cualquier infraestructura que pueda ejecutar Node.js. • https://github.com/parse-community/parse-server/security/advisories/GHSA-h423-w6qv-2wj3 • CWE-1284: Improper Validation of Specified Quantity in Input •
CVSS: 3.7EPSS: 0%CPEs: 2EXPL: 0CVE-2022-39231 – Parse Server subject to Improper Authentication allowing Auth adapter app ID validation to be circumvented
https://notcve.org/view.php?id=CVE-2022-39231
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In versions prior to 4.10.16, or from 5.0.0 to 5.2.6, validation of the authentication adapter app ID for _Facebook_ and _Spotify_ may be circumvented. Configurations which allow users to authenticate using the Parse Server authentication adapter where `appIds` is set as a string instead of an array of strings authenticate requests from an app with a different app ID than the one specified in the `appIds` configuration. For this vulnerability to be exploited, an attacker needs to be assigned an app ID by the authentication provider which is a sub-set of the server-side configured app ID. This issue is patched in versions 4.10.16 and 5.2.7. • https://github.com/parse-community/parse-server/security/advisories/GHSA-r657-33vp-gp22 • CWE-287: Improper Authentication •
CVSS: 4.3EPSS: 0%CPEs: 2EXPL: 0CVE-2022-39225 – Parse Server subject to Incorrect Resource Transfer Between Spheres
https://notcve.org/view.php?id=CVE-2022-39225
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In versions prior to 4.10.15, or 5.0.0 and above prior to 5.2.6, a user can write to the session object of another user if the session object ID is known. For example, an attacker can assign the session object to their own user by writing to the `user` field and then read any custom fields of that session object. Note that assigning a session to another user does not usually change the privileges of either of the two users, and a user cannot assign their own session to another user. This issue is patched in version 4.10.15 and above, and 5.2.6 and above. • https://github.com/parse-community/parse-server/security/advisories/GHSA-6w4q-23cf-j9jp • CWE-669: Incorrect Resource Transfer Between Spheres •