Update dependency marked to v4 [SECURITY] #684
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.1.1
->4.0.10
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.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.v1.2.9
Compare Source
Bug Fixes
v1.2.8
Compare Source
Bug Fixes
v1.2.7
Compare Source
Bug Fixes
v1.2.6
Compare Source
Bug Fixes
possible breaking change: When using the block.heading rule the text provided in capture group 2 will not be trimmed of whitespace.
v1.2.5
Compare Source
Bug Fixes
v1.2.4
Compare Source
Bug Fixes
Possible Breaking Change: When using the inline.del rule the text is provided in capture group 2 instead of 1.
v1.2.3
Compare Source
Bug Fixes
v1.2.2
Compare Source
Bug Fixes
v1.2.1
Compare Source
re-release of v 1.1.2 since semantic release picked up the wrong version
v1.2.0
: 1.2.0Compare Source
Features
Fixes
Dependencies
Documentation
v1.1.2
Compare Source
Bug Fixes
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.