Prototype pollution via path-keyed directory object
Published Oct 12, 2022 · Updated May 15, 2025
Prototype pollution in tschaub gh-pages before 5.0.0 allows attackers to alter object prototypes via crafted file paths. The uniqueDirs function splits each file path into directory segments and stores partial paths as keys on a plain object, causing prototype-property keys to be handled through Object.prototype instead of as inert directory data. Reachability requires a consuming build or publish workflow to pass attacker-controlled filenames into uniqueDirs; public sources document no demonstrated consequence beyond prototype modification.
Summary
What happened
Prototype pollution in tschaub gh-pages before 5.0.0 allows attackers to alter object prototypes via crafted file paths. The uniqueDirs function splits each file path into directory segments and stores partial paths as keys on a plain object, causing prototype-property keys to be handled through Object.prototype instead of as inert directory data. Reachability requires a consuming build or publish workflow to pass attacker-controlled filenames into uniqueDirs; public sources document no demonstrated consequence beyond prototype modification.
The record
- CVE
- CVE-2022-37611
- Published
- Oct 12, 2022
- Updated
- May 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 12, 2022CVE publishedPublication date reported by the CVE source.
- May 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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