Prototype pollution via unsanitized handler parameters
Published Jun 17, 2022 · Updated Sep 17, 2024
Prototype Pollution in Querymen allows remote attackers to alter object prototypes via crafted parameters passed to the exported handler function. The handler(type, name, fn) path accepts attacker-controlled values without sanitization, allowing properties to be written onto object prototypes in consuming Node.js applications. Exploitation requires an application to expose those parameters to remote attackers; the record describes confidentiality impact but does not establish integrity or availability effects.
Summary
What happened
Prototype Pollution in Querymen allows remote attackers to alter object prototypes via crafted parameters passed to the exported handler function. The handler(type, name, fn) path accepts attacker-controlled values without sanitization, allowing properties to be written onto object prototypes in consuming Node.js applications. Exploitation requires an application to expose those parameters to remote attackers; the record describes confidentiality impact but does not establish integrity or availability effects.
The record
- CVE
- CVE-2022-25871
- Published
- Jun 17, 2022
- Updated
- Sep 17, 2024
- Vendor
- Diego Haz
- Product
- Querymen
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
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
No public exploit references are available in this record.
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