Prototype pollution via unsafe property copy
Published Jun 12, 2023 · Updated Jan 6, 2025
Prototype Pollution in progressbar.js before 1.1.1 allows attackers to alter JavaScript object prototypes via crafted input. The extend function in src/utils.js iterates source properties and assigns each value to the destination without blocking prototype-mutating keys such as proto, enabling pollution of shared object state. Exploitation requires a consuming application to pass attacker-controlled data into this merge routine; resulting integrity or availability effects depend on downstream gadgets.
Summary
What happened
Prototype Pollution in progressbar.js before 1.1.1 allows attackers to alter JavaScript object prototypes via crafted input. The extend function in src/utils.js iterates source properties and assigns each value to the destination without blocking prototype-mutating keys such as proto, enabling pollution of shared object state. Exploitation requires a consuming application to pass attacker-controlled data into this merge routine; resulting integrity or availability effects depend on downstream gadgets.
The record
- CVE
- CVE-2023-26133
- Published
- Jun 12, 2023
- Updated
- Jan 6, 2025
- Vendor
- Kimmo Brunfeldt
- Product
- progressbar.js
- Classifications
- CWE-1321, T1129
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 12, 2023CVE publishedPublication date reported by the CVE source.
- Jan 6, 2025Record 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=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
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