Pug Code Gen
Approved changes feed: RSS · Atom
cpe:2.3:a:pugjs:pug-code-gen:*:*:*:*:*:node.js:*:*
part: a version: * update: *
| Vendor | Pugjs (caf74a94-63cc-518f-9eb7-ea4c93a55352) |
|---|---|
| Product | Pug Code Gen (19b7da93-59b0-51ca-843f-75fee8b45c57) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-21353 |
vulnerable | 2026-06-08 05:29:11.743991 |
Remote code execution in pug
MEDIUM (6.8)
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.
Published: 2021-03-03T01:50:18.000Z
Updated: 2025-04-16T22:10:03.957Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.