Prototype pollution via unsafe __proto__ section handling
Published Jul 25, 2022 · Updated Sep 16, 2024
Prototype pollution in properties-reader before 2.2.0 allows remote attackers to alter JavaScript object prototypes via crafted properties files. The set() parser treated a proto section name as a normal object key and assigned nested values into the inherited prototype instead of creating an isolated object. Exploitation requires the application to process attacker-controlled properties content; polluted properties can then affect security-sensitive code and availability.
Summary
What happened
Prototype pollution in properties-reader before 2.2.0 allows remote attackers to alter JavaScript object prototypes via crafted properties files. The set() parser treated a proto section name as a normal object key and assigned nested values into the inherited prototype instead of creating an isolated object. Exploitation requires the application to process attacker-controlled properties content; polluted properties can then affect security-sensitive code and availability.
The record
- CVE
- CVE-2020-28471
- Published
- Jul 25, 2022
- Updated
- Sep 16, 2024
- Vendor
- Steve King
- Product
- properties-reader
- Classifications
- CWE-1321, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 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=unspecified <2.2.0
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.
Public exploit references
- properties-reader __proto__ pollution 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