Service crash via recursive __proto__ object merge
Published Mar 1, 2021 · Updated Apr 30, 2025
Prototype pollution in FireBlink Object Collider 1.0.0 through 1.0.3 allows remote attackers to crash a host application or execute code. The collideObjects loop recursively merges an attacker-controlled proto key into the destination prototype instead of rejecting that key. Exploitation requires a consuming application to pass attacker-controlled objects to the merge API; a crash is direct, while code execution requires a suitable application gadget.
Summary
What happened
Prototype pollution in FireBlink Object Collider 1.0.0 through 1.0.3 allows remote attackers to crash a host application or execute code. The collideObjects loop recursively merges an attacker-controlled proto key into the destination prototype instead of rejecting that key. Exploitation requires a consuming application to pass attacker-controlled objects to the merge API; a crash is direct, while code execution requires a suitable application gadget.
The record
- CVE
- CVE-2021-25914
- Published
- Mar 1, 2021
- Updated
- Apr 30, 2025
- Vendor
- FireBlink
- Product
- Object Collider
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 1, 2021CVE publishedPublication date reported by the CVE source.
- Apr 30, 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=1.0.0, 1.0.1, 1.0.2, 1.0.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream prototype-pollution regression testproof of concept · demonstrated
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