CVE-2023-41058
What it is
Parse Server is an open source backend server. In affected versions the Parse Cloud trigger `beforeFind` is not invoked in certain conditions of `Parse.Query`. This can pose a vulnerability for deployments where the `beforeFind` trigger is used as a security layer to modify the incoming query. The vulnerability has been fixed by refactoring the internal query pipeline for a more concise code structure and implementing a patch to ensure the `beforeFind` trigger is invoked. This fix was introduced in commit `be4c7e23c6` and has been included in releases 6.2.2 and 5.5.5. Users are advised to upgrade. Users unable to upgrade should make use of parse server's security layers to manage access levels with Class-Level Permissions and Object-Level Access Control that should be used instead of custom security layers in Cloud Code triggers.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure.
- Exploit odds
- 0.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.8% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.8% · EPSS, next 30 days
- Weakness
- CWE-670
- Record status
- Modified
Affected
- Parseplatform parse-server < 5.5.5
- Parseplatform parse-server < 6.2.2
Attack profile CVSS 3.1 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-41058.md and follow it. Check whether this project is affected by CVE-2023-41058. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/parse-community/parse-server/commit/be4c7e23c63a2fb690685665cebed0de26be05c5
- https://github.com/parse-community/parse-server/releases/tag/5.5.5
- https://github.com/parse-community/parse-server/releases/tag/6.2.2
- https://github.com/parse-community/parse-server/security/advisories/GHSA-fcv6-fg5r-jm9q
- https://github.com/parse-community/parse-server/commit/be4c7e23c63a2fb690685665cebed0de26be05c5
- https://github.com/parse-community/parse-server/releases/tag/5.5.5
- https://github.com/parse-community/parse-server/releases/tag/6.2.2
- https://github.com/parse-community/parse-server/security/advisories/GHSA-fcv6-fg5r-jm9q
References
- https://docs.parseplatform.org/parse-server/guide/#security
- https://github.com/parse-community/parse-server/commit/be4c7e23c63a2fb690685665cebed0de26be05c5
- https://github.com/parse-community/parse-server/releases/tag/5.5.5
- https://github.com/parse-community/parse-server/releases/tag/6.2.2
- https://github.com/parse-community/parse-server/security/advisories/GHSA-fcv6-fg5r-jm9q
- https://docs.parseplatform.org/parse-server/guide/#security
- https://github.com/parse-community/parse-server/commit/be4c7e23c63a2fb690685665cebed0de26be05c5
- https://github.com/parse-community/parse-server/releases/tag/5.5.5
- https://github.com/parse-community/parse-server/releases/tag/6.2.2
- https://github.com/parse-community/parse-server/security/advisories/GHSA-fcv6-fg5r-jm9q