Service disruption via unchecked recursive object keys
Published Jun 17, 2022 · Updated Sep 16, 2024
Prototype pollution in Mout mout 1.2.3 and earlier allows remote attackers to disrupt consuming applications via crafted object keys. The deepFillIn and deepMixIn routines recursively use unchecked keys to access target objects, permitting constructor.prototype paths to alter inherited properties. Exposure requires an application to pass attacker-controlled objects into an affected recursive merge, and the reported consequence is an application crash or other service interruption.
Summary
What happened
Prototype pollution in Mout mout 1.2.3 and earlier allows remote attackers to disrupt consuming applications via crafted object keys. The deepFillIn and deepMixIn routines recursively use unchecked keys to access target objects, permitting constructor.prototype paths to alter inherited properties. Exposure requires an application to pass attacker-controlled objects into an affected recursive merge, and the reported consequence is an application crash or other service interruption.
The record
- CVE
- CVE-2022-21213
- Published
- Jun 17, 2022
- Updated
- Sep 16, 2024
- Vendor
- Mout
- Product
- mout
- Classifications
- CWE-1321, CAPEC-77
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=0 <unspecified
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