Update dependency marked to v4 [SECURITY] - abandoned

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
marked (source)	1.2.9 -> 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:

• Open an issue in marked

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.

import * as marked from 'marked';

console.log(marked.parse(`[x]: x

\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](`));

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?

• https://marked.js.org/using_advanced#workers
• 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:

• Open an issue in marked

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.

import * as marked from "marked";

marked.parse(`[x]:${' '.repeat(1500)}x ${' '.repeat(1500)} x`);

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?

• https://marked.js.org/using_advanced#workers
• 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:

• Open an issue in marked

---

Release Notes

markedjs/marked

v4.0.10

Compare Source

Bug Fixes

• security: fix redos vulnerabilities (8f80657)

v4.0.9

Compare Source

Bug Fixes

• retain line breaks in tokens properly (#​2341) (a9696e2)

v4.0.8

Compare Source

Bug Fixes

• spaces on a newline after a table (#​2319) (f82ea2c)

v4.0.7

Compare Source

Bug Fixes

• Fix every third list item broken (#​2318) (346b162), closes #​2314

v4.0.6

Compare Source

Bug Fixes

• speed up parsing long lists (#​2302) (e0005d8)

v4.0.5

Compare Source

Bug Fixes

• table after paragraph without blank line (#​2298) (5714212)

v4.0.4

Compare Source

Bug Fixes

• fix cli (#​2294) (ab2977a)

v4.0.3

Compare Source

Bug Fixes

• build min from umd (#​2283) (ea26ea9)

v4.0.2

Compare Source

Bug Fixes

• Create separate CJS and UMD builds (#​2281) (62faaf4)

v4.0.1

Compare Source

Bug Fixes

• Set commonJS code as main in package.json (#​2276) (7e636d5)

v4.0.0

Compare Source

Bug Fixes

• Convert to ESM (#​2227) (4afb228)

BREAKING CHANGES

• Default export removed. Use import { marked } from 'marked' or const { marked } = require('marked') instead.
• /lib/marked.js removed. Use /marked.min.js in script tag instead.
• When using marked in a script tag use marked.parse(...) instead of marked(...)

v3.0.8

Compare Source

Bug Fixes

• walkTokens uses marked as this (#​2251) (2da5885)

v3.0.7

Compare Source

Bug Fixes

• use named exports only for ESM build (#​2226)

v3.0.6

Compare Source

Bug Fixes

• Remove esm interop (#​2225) (4bc9121)

v3.0.5

Compare Source

Bug Fixes

• Expose named exports for ESM build (#​2223) (3959651)

v3.0.4

Compare Source

Bug Fixes

• fix detection of orphaned emStrong delimiters (#​2203) (7792adc)

v3.0.3

Compare Source

Bug Fixes

• fix space at end of table line (#​2201) (910f0f0)

v3.0.2

Compare Source

Bug Fixes

• stop table at lines with only whitespace (#​2188) (21268ab)

v3.0.1

Compare Source

Bug Fixes

• fix gfm urls after link (#​2186) (e03b5c1)

v3.0.0

Compare Source

Bug Fixes

• Tokenizers lex their own child tokens (#​2124) (288f1cb)
• Add module field to package.json (#​2143) (edc2e6d)
• Drop node 10 support (#​2157) (433b16f)
• Full Commonmark compliance for Lists (#​2112) (eb33d3b)
• Refactor table tokens (#​2166) (bc400ac)

BREAKING CHANGES

• Drop support for node 10.
• Add module field to package.json

---

• Tokenizers will create their own tokens with this.lexer.inline(text, tokens). The inline function will queue the token creation until after all block tokens are created.
• Extensions tokenizer this object will include the lexer as a property. this.inlineTokens becomes this.lexer.inline.
• Extensions renderer this object will include the parser as a property. this.parseInline becomes this.parser.parseInline.
• tag and inlineText tokenizer function signatures have changed.

---

• nptable tokenizer is removed and merged with table tokenizer.
• table tokens header property changed to contain an array of objects for each header cell with text and tokens properties.
• table tokens cells property changed to rows and is an array of rows where each row contains an array of objects for each cell with text and tokens properties.

v2 table token:

{
  "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 table token:

{
  "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.3

Compare Source

Bug Fixes

• update commonmark spec to v0.30 (#​2113) (62d6a0e)

v2.1.2

Compare Source

Bug Fixes

• add Node.js 10 to CI and loosen engines field (#​2119) (8659353)

v2.1.1

Compare Source

Bug Fixes

• fix node v12 (#​2109) (af14068)

v2.1.0

Compare Source

Features

• Custom Tokenizer/Renderer extensions (#​2043) (5be9d6d)

v2.0.7

Compare Source

Bug Fixes

• em strong (#​2075) (825a9f8)

v2.0.6

Compare Source

Bug Fixes

• fix autolink email after single space (#​2073) (6c9a899)

v2.0.5

Compare Source

Bug Fixes

• call walkTokens when calling marked with a callback(#​2060) (1d97308)

v2.0.4

Compare Source

Bug Fixes

• Fix indented markdown in html (#​2052) (6435ac9)

v2.0.3

Compare Source

Bug Fixes

• actually add a type property to the def token (#​2002) (47e65cf)

v2.0.2

Compare Source

Bug Fixes

• add type property on def token (#​2001) (009427f)

v2.0.1

Compare Source

Bug Fixes

• fix items between lists (#​1936) (46cdfc1)

v2.0.0

Compare Source

Bug Fixes

• Join adjacent inlineText tokens (#​1926) (f848e77)
• Total rework of Emphasis/Strong (#​1864) (7293251)

BREAKING CHANGES

• em and strong tokenizers have been merged into one emStrong tokenizer.
• code and text tokenizers do not get passed all tokens as a second parameter.
• No longer supporting IE 11. IE 11 may still work but we are not committed to making sure it works with every update. We still provide an es5 version in 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/umetsu/blog/GWUMCacqvkuHeBycdyvfhXDvLVwB
✅ Preview: https://blog-git-renovate-npm-marked-vulnerability-umetsu.vercel.app

[Deployment for 483dcdf failed]

[renovate]

Edited/Blocked Notification

Renovate 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.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.