[Security] Bump marked from 0.3.2 to 2.1.3

[dependabot-preview]

Bumps marked from 0.3.2 to 2.1.3. This update includes security fixes.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects marked marked is an application that is meant to parse and compile markdown. Due to the way that marked 0.3.5 and earlier parses input, specifically HTML entities, it's possible to bypass marked's content injection protection (sanitize: true) to inject a javascript: URL. This flaw exists because NNanything; gets parsed to what it could and leaves the rest behind, resulting in just anything; being left.

Affected versions: < 0.3.6

Sourced from The Node Security Working Group.

Sanitization bypass using HTML Entities marked is an application that is meant to parse and compile markdown.

Due to the way that marked parses input, specifically HTML entities, it's possible to bypass marked's content injection protection (sanitize: true) to inject a javascript: URL.

This flaw exists because NNanything; gets parsed to what it could and leaves the rest behind, resulting in just anything; being left.

For example:

If a malicious user could provide this input to the application javascript֍ocument;alert(1) resulting in a valid link, that when a user clicked it would execute alert(1).

Affected versions: <=0.3.5

Sourced from The Node Security Working Group.

VBScript Content Injection Marked 0.3.2 and earlier is vulnerable to content injection even when sanitize: true is enabled.

[xss link](vbscript:alert(1))

will get a link

xss link

this script does not work in IE 11 edge mode, but works in IE 10 compatibility view.

Affected versions: <=0.3.2

Sourced from The Node Security Working Group.

Regular Expression Denial of Service Marked 0.3.3 and earlier is vulnerable to regular expression denial of service (ReDoS) when certain types of input are passed in to be parsed.

"The Regular expression Denial of Service (ReDoS) is a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size). An attacker can then cause a program using a Regular Expression to enter these extreme situations and then hang for a very long time." [1]

Marked's catastrophic backtracking issue for the em inline rule has now been patched in 0.3.4.

Affected versions: <=0.3.3

Sourced from The GitHub Security Advisory Database.

Regular Expression Denial of Service in marked Versions of marked prior to 0.6.2 and later than 0.3.14 are vulnerable to Regular Expression Denial of Service. Email addresses may be evaluated in quadratic time, allowing attackers to potentially crash the node process due to resource exhaustion.

Recommendation

Upgrade to version 0.6.2 or later.

Affected versions: < 0.3.18

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects marked marked version 0.3.6 and earlier is vulnerable to an XSS attack in the data: URI parser.

Affected versions: < 0.3.7

Sourced from The GitHub Security Advisory Database.

High severity vulnerability that affects marked The marked module is vulnerable to a regular expression denial of service. Based on the information published in the public issue, 1k characters can block for around 6 seconds.

Affected versions: <0.3.9

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects marked A Regular expression Denial of Service (ReDoS) vulnerability in the file marked.js of the marked npm package (tested on version 0.3.7) allows a remote attacker to overload and crash a server by passing a maliciously crafted string.

Affected versions: < 0.3.9

Sourced from The GitHub Security Advisory Database.

High severity vulnerability that affects marked The marked module is vulnerable to a regular expression denial of service. Based on the information published in the public issue, 1k characters can block for around 6 seconds.

Affected versions: < 0.3.9

Release notes

Sourced from marked's releases.

v2.1.3

2.1.3 (2021-06-25)

Bug Fixes

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

v2.1.2

2.1.2 (2021-06-22)

Bug Fixes

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

v2.1.1

2.1.1 (2021-06-16)

Bug Fixes

• fix node v12 (#2109) (af14068)

v2.1.0

2.1.0 (2021-06-15)

Features

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

v2.0.7

2.0.7 (2021-06-01)

Bug Fixes

• em strong (#2075) (825a9f8)

v2.0.6

2.0.6 (2021-05-27)

Bug Fixes

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

v2.0.5

2.0.5 (2021-05-21)

... (truncated)

Commits

• 3a81bde chore(release): 2.1.3 [skip ci]
• a90848f 🗜️ build [skip ci]
• 62d6a0e fix: update commonmark spec to v0.30 (#2113)
• c7b4664 chore(release): 2.1.2 [skip ci]
• 8659353 fix: add Node.js 10 to CI and loosen engines field (#2119)
• 30c3d05 chore(deps-dev): Bump @​babel/core from 7.14.5 to 7.14.6 (#2118)
• 7c1fa84 chore(deps-dev): Bump eslint from 7.28.0 to 7.29.0 (#2115)
• b611bb1 chore(deps-dev): Bump rollup from 2.51.2 to 2.52.2 (#2116)
• 8321e89 chore(deps-dev): Bump semantic-release from 17.4.3 to 17.4.4 (#2117)
• da1c57f chore(docs): add extensions link to nav links (#2105)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by tonybrix, a new releaser for marked since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)