Arbitrary JavaScript execution via inherited template settings
Published Mar 15, 2020 · Updated Aug 4, 2024
Code injection in Laura Doktorova doT 1.1.2 allows attackers to execute arbitrary JavaScript through a crafted template or polluted prototype. The compiler passes its varname setting to Function(), while doT.process accepts an inherited templateSettings property and uses its attacker-controlled varname as a generated function parameter. Exploitation requires control of a compiled template or prior pollution of Object.prototype, and injected code runs in the consuming application's context.
Summary
What happened
Code injection in Laura Doktorova doT 1.1.2 allows attackers to execute arbitrary JavaScript through a crafted template or polluted prototype. The compiler passes its varname setting to Function(), while doT.process accepts an inherited templateSettings property and uses its attacker-controlled varname as a generated function parameter. Exploitation requires control of a compiled template or prior pollution of Object.prototype, and injected code runs in the consuming application's context.
The record
- CVE
- CVE-2020-8141
- Published
- Mar 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Laura Doktorova
- Product
- doT
- Classifications
- CWE-94, T1059.007
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=1.1.2
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
- Prototype-pollution code-execution 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