Update dependency marked to v4 [SECURITY] #955
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.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot].This notice will be removed on 2025-10-07.
This PR contains the following updates:
0.6.1->4.0.10^2.0.0->^4.0.0^0.6.1->^4.0.0^0.8.0->^4.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
GHSA-ch52-vgq2-943f
Affected versions of
markedare vulnerable to Regular Expression Denial of Service (ReDoS). The_labelsubrule may significantly degrade parsing performance of malformed input.Recommendation
Upgrade to version 0.7.0 or later.
CVE-2022-21680
Impact
What kind of vulnerability is it?
Denial of service.
The regular expression
block.defmay 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.reflinkSearchmay 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 (marked)
v4.0.10Compare Source
Bug Fixes
v4.0.9Compare Source
Bug Fixes
v4.0.8Compare Source
Bug Fixes
v4.0.7Compare Source
Bug Fixes
v4.0.6Compare Source
Bug Fixes
v4.0.5Compare Source
Bug Fixes
v4.0.4Compare Source
Bug Fixes
v4.0.3Compare Source
Bug Fixes
v4.0.2Compare Source
Bug Fixes
v4.0.1Compare Source
Bug Fixes
maininpackage.json(#2276) (7e636d5)v4.0.0Compare Source
Bug Fixes
BREAKING CHANGES
import { marked } from 'marked'orconst { marked } = require('marked')instead./lib/marked.jsremoved. Use/marked.min.jsin script tag instead.marked.parse(...)instead ofmarked(...)v3.0.8Compare Source
Bug Fixes
v3.0.7Compare Source
Bug Fixes
v3.0.6Compare Source
Bug Fixes
v3.0.5Compare Source
Bug Fixes
v3.0.4Compare Source
Bug Fixes
v3.0.3Compare Source
Bug Fixes
v3.0.2Compare Source
Bug Fixes
v3.0.1Compare Source
Bug Fixes
v3.0.0Compare Source
Bug Fixes
BREAKING CHANGES
this.lexer.inline(text, tokens). Theinlinefunction will queue the token creation until after all block tokens are created.thisobject will include thelexeras a property.this.inlineTokensbecomesthis.lexer.inline.thisobject will include theparseras a property.this.parseInlinebecomesthis.parser.parseInline.tagandinlineTexttokenizer function signatures have changed.nptabletokenizer is removed and merged withtabletokenizer.tabletokensheaderproperty changed to contain an array of objects for each header cell withtextandtokensproperties.tabletokenscellsproperty changed torowsand is an array of rows where each row contains an array of objects for each cell withtextandtokensproperties.v2
tabletoken:{ "type": "table", "align": [null, null], "raw": "| a | b |\n|---|---|\n| 1 | 2 |\n", "header": ["a", "b"], "cells": [["1", "2"]], "tokens": { "header": [ [{ "type": "text", "raw": "a", "text": "a" }], [{ "type": "text", "raw": "b", "text": "b" }] ], "cells": [[ [{ "type": "text", "raw": "1", "text": "1" }], [{ "type": "text", "raw": "2", "text": "2" }] ]] } }v3
tabletoken:{ "type": "table", "align": [null, null], "raw": "| a | b |\n|---|---|\n| 1 | 2 |\n", "header": [ { "text": "a", "tokens": [{ "type": "text", "raw": "a", "text": "a" }] }, { "text": "b", "tokens": [{ "type": "text", "raw": "b", "text": "b" }] } ], "rows": [ { "text": "1", "tokens": [{ "type": "text", "raw": "1", "text": "1" }] }, { "text": "2", "tokens": [{ "type": "text", "raw": "2", "text": "2" }] } ] }v2.1.3Compare Source
Bug Fixes
v2.1.2Compare Source
Bug Fixes
enginesfield (#2119) (8659353)v2.1.1Compare Source
Bug Fixes
v2.1.0Compare Source
Features
v2.0.7Compare Source
Bug Fixes
v2.0.6Compare Source
Bug Fixes
v2.0.5Compare Source
Bug Fixes
v2.0.4Compare Source
Bug Fixes
v2.0.3Compare Source
Bug Fixes
typeproperty to thedeftoken (#2002) (47e65cf)v2.0.2Compare Source
Bug Fixes
v2.0.1Compare Source
Bug Fixes
v2.0.0Compare Source
Bug Fixes
BREAKING CHANGES
emandstrongtokenizers have been merged into oneemStrongtokenizer.codeandtexttokenizers do not get passed all tokens as a second parameter.lib/marked.jsbut some pollyfills may be needed for IE 11 in the future.v1.2.9Compare Source
Bug Fixes
v1.2.8Compare Source
Bug Fixes
v1.2.7Compare Source
Bug Fixes
v1.2.6Compare 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.5Compare Source
Bug Fixes
v1.2.4Compare 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.3Compare Source
Bug Fixes
v1.2.2Compare Source
Bug Fixes
v1.2.1Compare 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.2Compare Source
Bug Fixes
v1.1.1: 1.1.1Compare Source
Fixes
)delimiter #1704Docs
Scripts
npm run rules#1726v1.1.0: 1.1.0Compare Source
Features
walkTokensoption #1664Fixes
renderer.codeincludes space at beginning of each line of code #1645browserfield inpackage.jsonpointing to es5 output #1661Docs
tokenizerto option docs #1662v1.0.0: 1.0.0Compare Source
Breaking changes
marked.lexeroutput #1627Tokenizerto allow extending token creation #1637Features
marked.use()method to extend options #1646Fixes
_) breaks links containing underscores #1641Docs
CI
v0.8.2: 0.8.2Compare Source
Fixes
Docs
v0.8.1: 0.8.1Compare Source
Fixes
marked --help#1588v0.8.0: 0.8.0Compare Source
Breaking changes
Fixes
baseUrloption #1526Docs
Dev Dependencies
v0.7.0: 0.7.0Compare Source
Security
paragraphandtexttokens #1504Breaking Changes
sanitizeandsanitizeroptions #1504fencesto CommonMark #1511tablesto GFM #1511tablesoption #1511Fixes
Tests
v0.6.3: 0.6.3Compare Source
Fixes
<em>issue with mixed content #1451breaks: true#1507Docs
DevOps
v0.6.2: 0.6.2Compare Source
Security
Fixes
Enhancements
listitemfunction #1440CLI
--testand fix argv parameters #1442--versionflag to print marked version #1448Testing
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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.