Remote code execution in pug
pugjs pug
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| pug npm |
|
|
| pug-code-gen npm |
|
|
pugjs pug
| Product | Affected | Fixed in |
|---|---|---|
| pug npm |
|
|
| pug-code-gen npm |
|
|
Pug is an npm package which is a high-performance template engine. In pug before version 3.0.1, if a remote attacker was able to control the `pretty` option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was possible for them to achieve remote code execution on the node.js backend. This is fixed in version 3.0.1. This advisory applies to multiple pug packages including "pug", "pug-code-gen". pug-code-gen has a backported fix at version 2.0.3. This advisory is not exploitable if there is no way for un-trusted input to be passed to pug as the `pretty` option, e.g. if you compile templates in advance before applying user input to them, you do not need to upgrade.
From the CVE record · GitHub_M
Pug and pug-code-gen are vulnerable when untrusted input can control the compiler's `pretty` option. A remote attacker who can supply that input can execute code on the Node.js backend; the issue is not exploitable if untrusted input cannot reach that option.
Check deployments using npm pug before 3.0.1 or pug-code-gen before 2.0.3 or from 3.0.0 up to, but not including, 3.0.2.