-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency marked to v4 [security] #46
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-marked-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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-marked-vulnerability
branch
from
August 30, 2021 09:31
b572908
to
726ec61
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v2 [security]
fix(deps): update dependency marked to v3 [security]
Aug 30, 2021
renovate
bot
force-pushed
the
renovate/npm-marked-vulnerability
branch
from
August 30, 2021 14:18
726ec61
to
a8ebec6
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v3 [security]
fix(deps): update dependency marked to v2 [security]
Aug 30, 2021
renovate
bot
force-pushed
the
renovate/npm-marked-vulnerability
branch
from
September 6, 2021 10:06
a8ebec6
to
390b0a2
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v2 [security]
fix(deps): update dependency marked to v3 [security]
Sep 6, 2021
renovate
bot
force-pushed
the
renovate/npm-marked-vulnerability
branch
from
September 6, 2021 11:07
390b0a2
to
e22f95f
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v3 [security]
fix(deps): update dependency marked to v2 [security]
Sep 6, 2021
renovate
bot
force-pushed
the
renovate/npm-marked-vulnerability
branch
from
September 9, 2021 09:01
e22f95f
to
33bfe2d
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v2 [security]
fix(deps): update dependency marked to v3 [security]
Sep 9, 2021
renovate
bot
changed the title
fix(deps): update dependency marked to v3 [security]
fix(deps): update dependency marked to v2 [security]
Sep 9, 2021
renovate
bot
force-pushed
the
renovate/npm-marked-vulnerability
branch
2 times, most recently
from
September 13, 2021 09:57
597db71
to
4d9e1a7
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v2 [security]
fix(deps): update dependency marked to v3 [security]
Sep 13, 2021
renovate
bot
force-pushed
the
renovate/npm-marked-vulnerability
branch
from
September 13, 2021 10:57
4d9e1a7
to
a0e6655
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v3 [security]
fix(deps): update dependency marked to v2 [security]
Sep 13, 2021
renovate
bot
force-pushed
the
renovate/npm-marked-vulnerability
branch
from
September 16, 2021 11:12
a0e6655
to
e80ce4c
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v2 [security]
fix(deps): update dependency marked to v3 [security]
Sep 16, 2021
renovate
bot
force-pushed
the
renovate/npm-marked-vulnerability
branch
from
September 16, 2021 14:48
e80ce4c
to
e587e34
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v3 [security]
fix(deps): update dependency marked to v2 [security]
Sep 16, 2021
renovate
bot
force-pushed
the
renovate/npm-marked-vulnerability
branch
from
October 18, 2021 18:38
e587e34
to
a4fdcd9
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v2 [security]
fix(deps): update dependency marked to v3 [security]
Oct 18, 2021
renovate
bot
force-pushed
the
renovate/npm-marked-vulnerability
branch
from
March 7, 2022 09:24
a4fdcd9
to
d6c2beb
Compare
renovate
bot
changed the title
fix(deps): update dependency marked to v3 [security]
fix(deps): update dependency marked to v4 [security]
Mar 7, 2022
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^1.2.9
->^4.0.0
GitHub Vulnerability Alerts
CVE-2021-21306
Impact
What kind of vulnerability is it? Who is impacted?
Regular expression Denial of Service
A Denial of Service attack can affect anyone who runs user generated code through
marked
.Patches
Has the problem been patched? What versions should users upgrade to?
patched in v2.0.0
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
None.
References
Are there any links users can visit to find out more?
https://github.com/markedjs/marked/issues/1927
https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS
For more information
If you have any questions or comments about this advisory:
CVE-2022-21680
Impact
What kind of vulnerability is it?
Denial of service.
The regular expression
block.def
may cause catastrophic backtracking against some strings.PoC is the following.
Who is impacted?
Anyone who runs untrusted markdown through marked and does not use a worker with a time limit.
Patches
Has the problem been patched?
Yes
What versions should users upgrade to?
4.0.10
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Do not run untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources.
References
Are there any links users can visit to find out more?
For more information
If you have any questions or comments about this advisory:
CVE-2022-21681
Impact
What kind of vulnerability is it?
Denial of service.
The regular expression
inline.reflinkSearch
may cause catastrophic backtracking against some strings.PoC is the following.
Who is impacted?
Anyone who runs untrusted markdown through marked and does not use a worker with a time limit.
Patches
Has the problem been patched?
Yes
What versions should users upgrade to?
4.0.10
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Do not run untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources.
References
Are there any links users can visit to find out more?
For more information
If you have any questions or comments about this advisory:
Release Notes
markedjs/marked
v4.2.12
Compare Source
Sorry for all of the quick releases. We were testing out different ways to build the files for releases. v4.2.5 - v4.2.12 have no changes to how marked works. The only addition is the version number in the comment in the build files.
Bug Fixes
v4.2.11
Compare Source
Bug Fixes
v4.2.10
Compare Source
Bug Fixes
v4.2.9
Compare Source
Bug Fixes
v4.2.8
Compare Source
v4.2.7
Compare Source
Bug Fixes
v4.2.6
Compare Source
Bug Fixes
v4.2.5
Compare Source
Bug Fixes
v4.2.4
Compare Source
Bug Fixes
v4.2.3
Compare Source
Bug Fixes
v4.2.2
Compare Source
Bug Fixes
v4.2.1
Compare Source
Bug Fixes
v4.2.0
Compare Source
Features
v4.1.1
Compare Source
Bug Fixes
v4.1.0
Compare Source
Features
v4.0.19
Compare Source
Bug Fixes
v4.0.18
Compare Source
Bug Fixes
v4.0.17
Compare Source
Bug Fixes
v4.0.16
Compare Source
Bug Fixes
v4.0.15
Compare Source
Bug Fixes
v4.0.14
Compare Source
Bug Fixes
v4.0.13
Compare Source
Bug Fixes
v4.0.12
Compare Source
Bug Fixes
v4.0.11
Compare Source
Bug Fixes
v4.0.10
Compare Source
Bug Fixes
v4.0.9
Compare Source
Bug Fixes
v4.0.8
Compare Source
Bug Fixes
v4.0.7
Compare Source
Bug Fixes
v4.0.6
Compare Source
Bug Fixes
v4.0.5
Compare Source
Bug Fixes
v4.0.4
Compare Source
Bug Fixes
v4.0.3
Compare Source
Bug Fixes
v4.0.2
Compare Source
Bug Fixes
v4.0.1
Compare Source
Bug Fixes
main
inpackage.json
(#2276) (7e636d5)v4.0.0
Compare Source
Bug Fixes
BREAKING CHANGES
import { marked } from 'marked'
orconst { marked } = require('marked')
instead./lib/marked.js
removed. Use/marked.min.js
in script tag instead.marked.parse(...)
instead ofmarked(...)
v3.0.8
Compare Source
Bug Fixes
v3.0.7
Compare Source
Bug Fixes
v3.0.6
Compare Source
Bug Fixes
v3.0.5
Compare Source
Bug Fixes
v3.0.4
Compare Source
Bug Fixes
v3.0.3
Compare Source
Bug Fixes
v3.0.2
Compare Source
Bug Fixes
v3.0.1
Compare Source
Bug Fixes
v3.0.0
Compare Source
Bug Fixes
BREAKING CHANGES
this.lexer.inline(text, tokens)
. Theinline
function will queue the token creation until after all block tokens are created.this
object will include thelexer
as a property.this.inlineTokens
becomesthis.lexer.inline
.this
object will include theparser
as a property.this.parseInline
becomesthis.parser.parseInline
.tag
andinlineText
tokenizer function signatures have changed.nptable
tokenizer is removed and merged withtable
tokenizer.table
tokensheader
property changed to contain an array of objects for each header cell withtext
andtokens
properties.table
tokenscells
property changed torows
and is an array of rows where each row contains an array of objects for each cell withtext
andtokens
properties.v2
table
token:v3
table
token:v2.1.3
Compare Source
Bug Fixes
v2.1.2
Compare Source
Bug Fixes
engines
field (#2119) (8659353)v2.1.1
Compare Source
Bug Fixes
v2.1.0
Compare Source
Features
v2.0.7
Compare Source
Bug Fixes
v2.0.6
Compare Source
Bug Fixes
v2.0.5
Compare Source
Bug Fixes
v2.0.4
Compare Source
Bug Fixes
v2.0.3
Compare Source
Bug Fixes
type
property to thedef
token (#2002) (47e65cf)v2.0.2
Compare Source
Bug Fixes
v2.0.1
Compare Source
Bug Fixes
v2.0.0
Compare Source
Bug Fixes
BREAKING CHANGES
em
andstrong
tokenizers have been merged into oneemStrong
tokenizer.code
andtext
tokenizers do not get passed all tokens as a second parameter.lib/marked.js
but some pollyfills may be needed for IE 11 in the future.Configuration
📅 Schedule: Branch creation - "" (UTC), 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.