Vulnerability identifier: #VU46732

Vulnerability risk: Medium

CVSSv3: 6.7 [CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:U/RL:U/RC:C]

CVE-ID: N/A

CWE-ID: CWE-285

Exploitation vector: Network

Exploit availability: No

Vulnerable software: Parse Server
Web applications / Modules and components for CMS

Vendor: Parse Community

Description

The vulnerability allows a remote attacker to bypass authorization checks.

The vulnerability exists when the affected software uses the REST api to create a new session token, that tokens is not set as restricted. A remote attacker can bypass authorization checks and gain access to target system.

Mitigation
Cybersecurity Help is currently unaware of any official solution to address this vulnerability.

Vulnerable software versions

Parse Server: 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 2.2.9, 2.2.10, 2.2.11, 2.2.12, 2.2.13, 2.2.14, 2.2.15, 2.2.16, 2.2.17, 2.2.18, 2.2.19, 2.2.20, 2.2.21, 2.2.22, 2.2.23, 2.2.24, 2.2.25, 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5, 2.3.6, 2.3.7, 2.3.8, 2.4.0, 2.4.1, 2.4.2, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.6.4, 2.6.5, 2.7.0, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.8.0, 2.8.1, 2.8.2, 2.8.3, 2.8.4, 3.0.0, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.2.0, 3.2.1, 3.2.2, 3.2.3, 3.3.0, 3.4.0, 3.4.1, 3.4.2, 3.4.3, 3.4.4, 3.5.0, 3.6.0, 3.7.0, 3.7.1, 3.7.2, 3.8.0, 3.9.0, 3.10.0, 4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.2.0, 4.3.0

CPE

• cpe:/a:parse_community:parse_server:4.3.0:
• cpe:/a:parse_community:parse_server:4.2.0:
• cpe:/a:parse_community:parse_server:4.1.0:
• cpe:/a:parse_community:parse_server:4.0.2:
• cpe:/a:parse_community:parse_server:4.0.1:
• cpe:/a:parse_community:parse_server:4.0.0:
• cpe:/a:parse_community:parse_server:3.10.0:
• cpe:/a:parse_community:parse_server:3.9.0:
• cpe:/a:parse_community:parse_server:3.8.0:
• cpe:/a:parse_community:parse_server:3.7.2:
• cpe:/a:parse_community:parse_server:3.7.1:
• cpe:/a:parse_community:parse_server:3.7.0:
• cpe:/a:parse_community:parse_server:3.6.0:
• cpe:/a:parse_community:parse_server:3.5.0:
• cpe:/a:parse_community:parse_server:3.4.4:
• cpe:/a:parse_community:parse_server:3.4.3:
• cpe:/a:parse_community:parse_server:3.4.2:
• cpe:/a:parse_community:parse_server:3.4.1:
• cpe:/a:parse_community:parse_server:3.4.0:
• cpe:/a:parse_community:parse_server:3.3.0:
• cpe:/a:parse_community:parse_server:3.2.3:
• cpe:/a:parse_community:parse_server:3.2.2:
• cpe:/a:parse_community:parse_server:3.2.1:
• cpe:/a:parse_community:parse_server:3.2.0:
• cpe:/a:parse_community:parse_server:3.1.3:
• cpe:/a:parse_community:parse_server:3.1.2:
• cpe:/a:parse_community:parse_server:3.1.1:
• cpe:/a:parse_community:parse_server:3.1.0:
• cpe:/a:parse_community:parse_server:3.0.0:
• cpe:/a:parse_community:parse_server:2.8.4:
• cpe:/a:parse_community:parse_server:2.8.3:
• cpe:/a:parse_community:parse_server:2.8.2:
• cpe:/a:parse_community:parse_server:2.8.1:
• cpe:/a:parse_community:parse_server:2.8.0:
• cpe:/a:parse_community:parse_server:2.7.4:
• cpe:/a:parse_community:parse_server:2.7.3:
• cpe:/a:parse_community:parse_server:2.7.2:
• cpe:/a:parse_community:parse_server:2.7.1:
• cpe:/a:parse_community:parse_server:2.7.0:
• cpe:/a:parse_community:parse_server:2.6.5:
• cpe:/a:parse_community:parse_server:2.6.4:
• cpe:/a:parse_community:parse_server:2.6.3:
• cpe:/a:parse_community:parse_server:2.6.2:
• cpe:/a:parse_community:parse_server:2.6.1:
• cpe:/a:parse_community:parse_server:2.6.0:
• cpe:/a:parse_community:parse_server:2.5.3:
• cpe:/a:parse_community:parse_server:2.5.2:
• cpe:/a:parse_community:parse_server:2.5.1:
• cpe:/a:parse_community:parse_server:2.5.0:
• cpe:/a:parse_community:parse_server:2.4.2:
• cpe:/a:parse_community:parse_server:2.4.1:
• cpe:/a:parse_community:parse_server:2.4.0:
• cpe:/a:parse_community:parse_server:2.3.8:
• cpe:/a:parse_community:parse_server:2.3.7:
• cpe:/a:parse_community:parse_server:2.3.6:
• cpe:/a:parse_community:parse_server:2.3.5:
• cpe:/a:parse_community:parse_server:2.3.4:
• cpe:/a:parse_community:parse_server:2.3.3:
• cpe:/a:parse_community:parse_server:2.3.2:
• cpe:/a:parse_community:parse_server:2.3.1:
• cpe:/a:parse_community:parse_server:2.3.0:
• cpe:/a:parse_community:parse_server:2.2.25:
• cpe:/a:parse_community:parse_server:2.2.24:
• cpe:/a:parse_community:parse_server:2.2.23:
• cpe:/a:parse_community:parse_server:2.2.22:
• cpe:/a:parse_community:parse_server:2.2.21:
• cpe:/a:parse_community:parse_server:2.2.20:
• cpe:/a:parse_community:parse_server:2.2.19:
• cpe:/a:parse_community:parse_server:2.2.18:
• cpe:/a:parse_community:parse_server:2.2.17:
• cpe:/a:parse_community:parse_server:2.2.16:
• cpe:/a:parse_community:parse_server:2.2.15:
• cpe:/a:parse_community:parse_server:2.2.14:
• cpe:/a:parse_community:parse_server:2.2.13:
• cpe:/a:parse_community:parse_server:2.2.12:
• cpe:/a:parse_community:parse_server:2.2.11:
• cpe:/a:parse_community:parse_server:2.2.10:
• cpe:/a:parse_community:parse_server:2.2.9:
• cpe:/a:parse_community:parse_server:2.2.8:
• cpe:/a:parse_community:parse_server:2.2.7:
• cpe:/a:parse_community:parse_server:2.2.6:
• cpe:/a:parse_community:parse_server:2.2.5:
• cpe:/a:parse_community:parse_server:2.2.4:
• cpe:/a:parse_community:parse_server:2.2.3:
• cpe:/a:parse_community:parse_server:2.2.2:
• cpe:/a:parse_community:parse_server:2.2.1:
• cpe:/a:parse_community:parse_server:2.2.0:
• cpe:/a:parse_community:parse_server:2.1.6:
• cpe:/a:parse_community:parse_server:2.1.5:
• cpe:/a:parse_community:parse_server:2.1.4:
• cpe:/a:parse_community:parse_server:2.1.3:
• cpe:/a:parse_community:parse_server:2.1.2:
• cpe:/a:parse_community:parse_server:2.1.1:
• cpe:/a:parse_community:parse_server:2.1.0:
• cpe:/a:parse_community:parse_server:2.0.8:
• cpe:/a:parse_community:parse_server:2.0.7:
• cpe:/a:parse_community:parse_server:2.0.6:
• cpe:/a:parse_community:parse_server:2.0.5:

External links
https://snyk.io/vuln/SNYK-JS-PARSESERVER-590116
https://github.com/parse-community/parse-server/issues/6612

---

Q & A

Can this vulnerability be exploited remotely?

Yes. This vulnerability can be exploited by a remote non-authenticated attacker via the Internet.

Is there known malware, which exploits this vulnerability?

No. We are not aware of malware exploiting this vulnerability.