Remote code execution via prototype pollution
Published Mar 11, 2022 · Updated Apr 22, 2025
Command injection in Parse Server before 4.10.7 allows remote attackers to execute arbitrary code through crafted REST request data. DatabaseController.js accepts prototype-sensitive keys such as constructor and proto in request objects, allowing attacker-controlled properties to reach BSON deserialization options. No authentication or user interaction is required, and the default MongoDB configuration is affected; successful exploitation gives code execution in the server process.
Summary
What happened
Command injection in Parse Server before 4.10.7 allows remote attackers to execute arbitrary code through crafted REST request data. DatabaseController.js accepts prototype-sensitive keys such as constructor and proto in request objects, allowing attacker-controlled properties to reach BSON deserialization options. No authentication or user interaction is required, and the default MongoDB configuration is affected; successful exploitation gives code execution in the server process.
The record
- CVE
- CVE-2022-24760
- Published
- Mar 11, 2022
- Updated
- Apr 22, 2025
- Vendor
- Parse Platform
- Product
- Parse Server
- Classifications
- CWE-74, CWE-1321, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.10.7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- huntr original proof-of-concept reportproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo