Parse-community parse-server
Parse Server 9.0.0 before 9.10.2-alpha.5 Transactional Batch Request Write Interference
Parse Server 5.4.0 before 8.6.96 and 9.0.0 before 9.10.2-alpha.5 shares transactional batch state across concurrent requests, letting any client's transactional batch request interfere with other clients' database writes. On PostgreSQL or MongoDB replica sets and sharded clusters, other clients' acknowledged writes are rolled back if the batch fails, and PostgreSQL transactions can remain open indefinitely, causing subsequent writes to fail.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.3high · scored by CNA · CWE-362
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
parse-community parse-server
- >= 9.0.0, < 9.10.2-alpha.5
Fixed in 9.10.2-alpha.5
parse-community parse-server
- >= 5.4.0, < 8.6.96
Fixed in 8.6.96
Mitigation
Upgrade parse-server to 9.10.2-alpha.5 or later.
Upgrade parse-server to 8.6.96 or later.
References
- Vendor advisory github.com/parse-community/parse-server/securi…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.