Object prototype modification via crafted XML keys
Published Sep 13, 2021 · Updated Aug 3, 2024
Prototype pollution in Fiznool body-parser-xml before 2.0.3 allows remote authenticated users to alter object prototypes via crafted XML. The XML middleware assigns parsed data to req.body without first removing top-level proto, constructor, and prototype keys. Low-privileged access to an XML-accepting route is required, and the resulting effect depends on downstream use of polluted properties.
Summary
What happened
Prototype pollution in Fiznool body-parser-xml before 2.0.3 allows remote authenticated users to alter object prototypes via crafted XML. The XML middleware assigns parsed data to req.body without first removing top-level proto, constructor, and prototype keys. Low-privileged access to an XML-accepting route is required, and the resulting effect depends on downstream use of polluted properties.
The record
- CVE
- CVE-2021-3666
- Published
- Sep 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Fiznool
- Product
- body-parser-xml
- Classifications
- CWE-1321, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=unspecified <2.0.3
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
- 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