Skip to content
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
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 22, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
marked (source) ^1.2.9 -> ^4.0.0 age adoption passing confidence

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.

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?

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.

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?

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
  • revert to build script in ci (d2ab474)

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
  • add version to build files (79b8c0b)

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
  • allow emStrong regex to consume more characters at once (#​2433) (35583c3)

v4.0.12

Compare Source

Bug Fixes

v4.0.11

Compare Source

Bug Fixes

v4.0.10

Compare Source

Bug Fixes
  • security: fix redos vulnerabilities (8f80657)

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

v4.0.0

Compare Source

Bug Fixes
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

v3.0.7

Compare Source

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

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
  • 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

v2.1.2

Compare Source

Bug Fixes

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

v2.0.2

Compare Source

Bug Fixes

v2.0.1

Compare Source

Bug Fixes

v2.0.0

Compare Source

Bug Fixes
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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jul 22, 2021
@renovate renovate bot force-pushed the renovate/npm-marked-vulnerability branch from b572908 to 726ec61 Compare August 30, 2021 09:31
@renovate 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 renovate bot force-pushed the renovate/npm-marked-vulnerability branch from 726ec61 to a8ebec6 Compare August 30, 2021 14:18
@renovate 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 renovate bot force-pushed the renovate/npm-marked-vulnerability branch from a8ebec6 to 390b0a2 Compare September 6, 2021 10:06
@renovate 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 renovate bot force-pushed the renovate/npm-marked-vulnerability branch from 390b0a2 to e22f95f Compare September 6, 2021 11:07
@renovate 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 renovate bot force-pushed the renovate/npm-marked-vulnerability branch from e22f95f to 33bfe2d Compare September 9, 2021 09:01
@renovate 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 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 renovate bot force-pushed the renovate/npm-marked-vulnerability branch 2 times, most recently from 597db71 to 4d9e1a7 Compare September 13, 2021 09:57
@renovate 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 renovate bot force-pushed the renovate/npm-marked-vulnerability branch from 4d9e1a7 to a0e6655 Compare September 13, 2021 10:57
@renovate 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 renovate bot force-pushed the renovate/npm-marked-vulnerability branch from a0e6655 to e80ce4c Compare September 16, 2021 11:12
@renovate 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 renovate bot force-pushed the renovate/npm-marked-vulnerability branch from e80ce4c to e587e34 Compare September 16, 2021 14:48
@renovate 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 renovate bot force-pushed the renovate/npm-marked-vulnerability branch from e587e34 to a4fdcd9 Compare October 18, 2021 18:38
@renovate 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 renovate bot force-pushed the renovate/npm-marked-vulnerability branch from a4fdcd9 to d6c2beb Compare March 7, 2022 09:24
@renovate renovate bot changed the title fix(deps): update dependency marked to v3 [security] fix(deps): update dependency marked to v4 [security] Mar 7, 2022
@renovate
Copy link
Author

renovate bot commented Mar 22, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant