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.
Upgrade to [email protected]
or [email protected]
or [email protected]
, which correctly sanitise the parameter.
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.
Original report: https://github.com/pugjs/pug/issues/3312
If you believe you have found other vulnerabilities, please DO NOT open an issue. Instead, you can follow the instructions in our Security Policy
github.com/pugjs/pug/commit/991e78f7c4220b2f8da042877c6f0ef5a4683be0
github.com/pugjs/pug/issues/3312
github.com/pugjs/pug/pull/3314
github.com/pugjs/pug/releases/tag/pug%403.0.1
github.com/pugjs/pug/security/advisories/GHSA-p493-635q-r6gr
nvd.nist.gov/vuln/detail/CVE-2021-21353
www.npmjs.com/package/pug
www.npmjs.com/package/pug-code-gen