Prototype pollution via prohibited INI section names
Published Jan 19, 2021 · Updated Sep 16, 2024
Prototype pollution in AWS SDK for JavaScript before 2.814.0 allows attackers to alter object prototypes through a crafted INI file. The loadSharedConfigFiles parser and @aws-sdk/shared-ini-file-loader before 1.0.0-rc.9 accept proto as a section name and assign its keys into a normal object, changing its inherited prototype. An application must parse an attacker-supplied shared configuration or credentials file; downstream consequences depend on how polluted properties are consumed.
Summary
What happened
Prototype pollution in AWS SDK for JavaScript before 2.814.0 allows attackers to alter object prototypes through a crafted INI file. The loadSharedConfigFiles parser and @aws-sdk/shared-ini-file-loader before 1.0.0-rc.9 accept proto as a section name and assign its keys into a normal object, changing its inherited prototype. An application must parse an attacker-supplied shared configuration or credentials file; downstream consequences depend on how polluted properties are consumed.
The record
- CVE
- CVE-2020-28472
- Published
- Jan 19, 2021
- Updated
- Sep 16, 2024
- Vendor
- Amazon Web Services
- Product
- AWS SDK for JavaScript
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2021CVE 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.814.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 loadSharedConfigFiles 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