This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 46
chore(deps): update dependency pug to v3 [security] - autoclosed #815
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
7 times, most recently
from
June 14, 2021 16:44
9b72f36
to
52b9a90
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
2 times, most recently
from
July 5, 2021 07:13
a758578
to
13e1730
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
2 times, most recently
from
July 30, 2021 09:45
cb8de6e
to
6dfc6ef
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
2 times, most recently
from
October 8, 2021 09:38
6fbde9e
to
e16ecbd
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
4 times, most recently
from
October 19, 2021 15:05
32f5dde
to
4a0cc4a
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
2 times, most recently
from
December 13, 2021 14:56
1472c55
to
72fd93b
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
from
January 19, 2022 09:18
72fd93b
to
e14fe64
Compare
renovate
bot
changed the title
chore(deps): update dependency pug to v3 [security]
chore(deps): update dependency pug to v3 [security] - autoclosed
Mar 12, 2022
renovate
bot
changed the title
chore(deps): update dependency pug to v3 [security] - autoclosed
chore(deps): update dependency pug to v3 [security]
Mar 15, 2022
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
4 times, most recently
from
March 18, 2022 15:36
e942b34
to
0c0e6ef
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
5 times, most recently
from
April 8, 2022 15:50
edab3a1
to
9d4bee9
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
from
May 2, 2022 10:42
9d4bee9
to
1773986
Compare
renovate
bot
changed the title
chore(deps): update dependency pug to v3 [security]
chore(deps): update dependency pug to v3 [security] - autoclosed
May 11, 2022
renovate
bot
changed the title
chore(deps): update dependency pug to v3 [security] - autoclosed
chore(deps): update dependency pug to v3 [security]
May 11, 2022
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
3 times, most recently
from
June 20, 2022 11:35
e6d8e49
to
9bba634
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
2 times, most recently
from
June 24, 2022 16:53
9eec5c1
to
5722c7e
Compare
renovate
bot
changed the title
chore(deps): update dependency pug to v3 [security]
chore(deps): update dependency pug to v3 [SECURITY]
Jun 27, 2022
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
from
June 27, 2022 08:31
5722c7e
to
4aad29f
Compare
renovate
bot
changed the title
chore(deps): update dependency pug to v3 [SECURITY]
chore(deps): update dependency pug to v3 [security]
Jun 28, 2022
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
2 times, most recently
from
August 3, 2022 12:30
b0132cc
to
ca7f8dc
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
2 times, most recently
from
September 12, 2022 15:56
25e9653
to
7151940
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
from
October 24, 2022 13:12
7151940
to
e189073
Compare
renovate
bot
force-pushed
the
renovate/npm-pug-vulnerability
branch
from
November 14, 2022 18:39
e189073
to
4615a13
Compare
renovate
bot
changed the title
chore(deps): update dependency pug to v3 [security]
chore(deps): update dependency pug to v3 [security] - autoclosed
Dec 9, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.0.3
->3.0.1
GitHub Vulnerability Alerts
CVE-2021-21353
Impact
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.Patches
Upgrade to
[email protected]
or[email protected]
or[email protected]
, which correctly sanitise the parameter.Workarounds
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.References
Original report: https://github.com/pugjs/pug/issues/3312
For more information
If you believe you have found other vulnerabilities, please DO NOT open an issue. Instead, you can follow the instructions in our Security Policy
Release Notes
pugjs/pug
v3.0.1
Compare Source
Bug Fixes
Sanitise the
pretty
option (#3314)If a malicious attacker could control the
pretty
option, it was possible for them to achieve remote code execution on the server rendering the template. All pug users should upgrade as soon as possible, see #3312 for more details.v3.0.0
Compare Source
Breaking Changes
read
plugins must now returnBuffer
if you want to support filters that userenderBuffer
(#3213)If you don't wish to support this advanced use case, you can continue returning
string
. If you did not provide aread
plugin, you do not need to do anything.The
minify
option on filters now requires you to install the relevant jstransformer (#3084)Currently we support:
Drop support for node 6 and 8 (#3243)
New Features
Support filters that apply to Buffers (#3213)
e.g.
You can then use the filter like:
// foo.pug include:png my-small-image.png
Add support for replacing code gen via a plugin with
generateCode
(#3230)Support
each ... of ...
loops (#3179)This requires an environment that supports the
for (const val of iterable)
syntax in JS. You can iterate over Maps, Sets etc. as well as arrays. There is also some destructuring of map keys:v2.0.4
: 2.0.4Compare Source
...
spread attributes when compiling to JSX N.B. this will not work when rendering to HTMLConfiguration
📅 Schedule: Branch creation - "" in timezone Europe/Paris, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.