Prototype pollution via unsafe transformation keys
Published Apr 6, 2020 · Updated Aug 4, 2024
Prototype pollution in TypeStack class-transformer before 0.3.1 allows attackers to modify Object.prototype through crafted input. The classToPlainFromExist transformation loop copies untrusted keys without rejecting proto or constructor, allowing inherited properties to be created or changed. Exploitation requires a consuming application to pass attacker-controlled object keys into this path, after which inherited properties can alter application logic.
Summary
What happened
Prototype pollution in TypeStack class-transformer before 0.3.1 allows attackers to modify Object.prototype through crafted input. The classToPlainFromExist transformation loop copies untrusted keys without rejecting proto or constructor, allowing inherited properties to be created or changed. Exploitation requires a consuming application to pass attacker-controlled object keys into this path, after which inherited properties can alter application logic.
The record
- CVE
- CVE-2020-7637
- Published
- Apr 6, 2020
- Updated
- Aug 4, 2024
- Vendor
- TypeStack
- Product
- class-transformer
- Classifications
- CWE-915, CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=All versions prior to version 0.3.1
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
- Snyk classToPlainFromExist proof of conceptproof 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