Parse Server up to 4.10.13/5.2.4 Field information disclosure

Summaryinfo

A vulnerability classified as problematic was found in Parse Server up to 4.10.13/5.2.4. This impacts an unknown function of the component Field Handler. Executing a manipulation can lead to information disclosure. This vulnerability is handled as CVE-2022-36079. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Parse Server up to 4.10.13/5.2.4. It has been declared as problematic. This vulnerability affects an unknown function of the component Field Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Internal fields (keys used internally by Parse Server, prefixed by `_`) and protected fields (user defined) can be used as query constraints. Internal and protected fields are removed by Parse Server and are only returned to the client using a valid master key. However, using query constraints, these fields can be guessed by enumerating until Parse Server, prior to versions 4.10.14 or 5.2.5, returns a response object. The patch available in versions 4.10.14 and 5.2.5 requires the maser key to use internal and protected fields as query constraints. As a workaround, implement a Parse Cloud Trigger `beforeFind` and manually remove the query constraints.

The weakness was released 09/08/2022 as GHSA-2m6g-crv8-p3c6. The advisory is shared for download at github.com. This vulnerability was named CVE-2022-36079 since 07/15/2022. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

Upgrading to version 4.10.14 or 5.2.5 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 634c44acd18f6ee6ec60fac89a2b602d92799bec is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

• Parse Server

Version

• 4.10.0
• 4.10.1
• 4.10.2
• 4.10.3
• 4.10.4
• 4.10.5
• 4.10.6
• 4.10.7
• 4.10.8
• 4.10.9
• 4.10.10
• 4.10.11
• 4.10.12
• 4.10.13
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion