Prototype pollution via unchecked __proto__ section parsing
Published Jul 25, 2022 · Updated Sep 16, 2024
Prototype pollution in js-ini before 1.3.0 allows remote attackers to modify shared object properties through a malicious INI file. The parse function treats a proto section as an ordinary result key, then assigns its entries through the inherited prototype accessor instead of isolating or rejecting that section. Exploitation requires a consuming application to parse attacker-controlled INI data, and further impact depends on downstream code using a polluted property.
Summary
What happened
Prototype pollution in js-ini before 1.3.0 allows remote attackers to modify shared object properties through a malicious INI file. The parse function treats a proto section as an ordinary result key, then assigns its entries through the inherited prototype accessor instead of isolating or rejecting that section. Exploitation requires a consuming application to parse attacker-controlled INI data, and further impact depends on downstream code using a polluted property.
The record
- CVE
- CVE-2020-28461
- Published
- Jul 25, 2022
- Updated
- Sep 16, 2024
- Vendor
- Denis Chernov
- Product
- js-ini
- Classifications
- CWE-1321, CAPEC-180, CAPEC-1, CAPEC-77
- 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 <1.3.0
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
- Snyk js-ini 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