Skip to content

Parse Server vulnerable to Prototype Pollution via Cloud Code Webhooks or Cloud Code Triggers

High severity GitHub Reviewed Published Nov 9, 2022 in parse-community/parse-server • Updated Aug 21, 2023

Package

npm parse-server (npm)

Affected versions

< 4.10.19
>= 5.0.0, < 5.3.2

Patched versions

4.10.19
5.3.2

Description

Impact

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.

Patches

Improved keyword detection.

Workarounds

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.

Collaborators

Mikhail Shcherbakov, Cristian-Alexandru Staicu and Musard Balliu working with Trend Micro Zero Day Initiative

References

References

@mtrezza mtrezza published to parse-community/parse-server Nov 9, 2022
Published to the GitHub Advisory Database Nov 9, 2022
Reviewed Nov 9, 2022
Published by the National Vulnerability Database Nov 10, 2022
Last updated Aug 21, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.372%
(73rd percentile)

Weaknesses

CVE ID

CVE-2022-41878

GHSA ID

GHSA-xprv-wvh7-qqqx

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.