Object property corruption via prototype pollution
Published Jun 30, 2021 · Updated Aug 3, 2024
Prototype pollution in ThinkJS think-helper before 1.1.3 allows remote attackers to modify inherited object properties through crafted input. The published advisory identifies uncontrolled object-attribute updates but does not disclose the affected helper function or precise assignment path. Reachability requires a consuming Node.js application to pass attacker-controlled attributes into the affected helper, enabling modification of properties inherited by other objects.
Summary
What happened
Prototype pollution in ThinkJS think-helper before 1.1.3 allows remote attackers to modify inherited object properties through crafted input. The published advisory identifies uncontrolled object-attribute updates but does not disclose the affected helper function or precise assignment path. Reachability requires a consuming Node.js application to pass attacker-controlled attributes into the affected helper, enabling modification of properties inherited by other objects.
The record
- CVE
- CVE-2021-32736
- Published
- Jun 30, 2021
- Updated
- Aug 3, 2024
- Vendor
- ThinkJS
- Product
- think-helper
- Classifications
- CWE-1321, CAPEC-77, CAPEC-180, CAPEC-1
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 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=< 1.1.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
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