chore(deps): update dependency marked to 4.0.10 [security] - abandoned

[renovate]

This PR contains the following updates:

Package	Change
marked	2.0.1 -> 4.0.10

GitHub Vulnerability Alerts

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

---

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.

[commit-lint]

Chore

• deps: update dependency marked to 4.0.10 [security] (5181ee2)

Contributors

renovate-bot

Commit-Lint commands

You can trigger Commit-Lint actions by commenting on this PR:

• @Commit-Lint merge patch will merge dependabot PR on "patch" versions (X.X.Y - Y change)
• @Commit-Lint merge minor will merge dependabot PR on "minor" versions (X.Y.Y - Y change)
• @Commit-Lint merge major will merge dependabot PR on "major" versions (Y.Y.Y - Y change)
• @Commit-Lint merge disable will desactivate merge dependabot PR
• @Commit-Lint review will approve dependabot PR
• @Commit-Lint stop review will stop approve dependabot PR

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: hubot-info-rut@4.0.5
npm WARN Found: semantic-release@17.4.2
npm WARN node_modules/semantic-release
npm WARN   dev semantic-release@"19.0.0" from the root project
npm WARN   7 more (@eclass/semantic-release-npm-github-config, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@"^15.9.0 || ^16.0.0 || ^17.0.0" from @eclass/semantic-release-npm-github-config@3.0.1
npm WARN node_modules/@eclass/semantic-release-npm-github-config
npm WARN   dev @eclass/semantic-release-npm-github-config@"3.0.1" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: hubot-info-rut@4.0.5
npm WARN Found: semantic-release@17.4.2
npm WARN node_modules/semantic-release
npm WARN   dev semantic-release@"19.0.0" from the root project
npm WARN   7 more (@eclass/semantic-release-npm-github-config, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/changelog@5.0.1
npm WARN node_modules/@semantic-release/changelog
npm WARN   dev @semantic-release/changelog@"5.0.1" from the root project
npm WARN   1 more (@eclass/semantic-release-npm-github-config)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: hubot-info-rut@4.0.5
npm WARN Found: semantic-release@17.4.2
npm WARN node_modules/semantic-release
npm WARN   dev semantic-release@"19.0.0" from the root project
npm WARN   7 more (@eclass/semantic-release-npm-github-config, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/changelog@5.0.1
npm WARN node_modules/@semantic-release/changelog
npm WARN   dev @semantic-release/changelog@"5.0.1" from the root project
npm WARN   1 more (@eclass/semantic-release-npm-github-config)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: hubot-info-rut@4.0.5
npm WARN Found: semantic-release@17.4.2
npm WARN node_modules/semantic-release
npm WARN   dev semantic-release@"19.0.0" from the root project
npm WARN   7 more (@eclass/semantic-release-npm-github-config, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/git@9.0.0
npm WARN node_modules/@semantic-release/git
npm WARN   dev @semantic-release/git@"9.0.0" from the root project
npm WARN   1 more (@eclass/semantic-release-npm-github-config)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: hubot-info-rut@4.0.5
npm WARN Found: semantic-release@17.4.2
npm WARN node_modules/semantic-release
npm WARN   dev semantic-release@"19.0.0" from the root project
npm WARN   7 more (@eclass/semantic-release-npm-github-config, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/git@9.0.0
npm WARN node_modules/@semantic-release/git
npm WARN   dev @semantic-release/git@"9.0.0" from the root project
npm WARN   1 more (@eclass/semantic-release-npm-github-config)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: hubot-info-rut@4.0.5
npm WARN Found: semantic-release@17.4.2
npm WARN node_modules/semantic-release
npm WARN   dev semantic-release@"19.0.0" from the root project
npm WARN   7 more (@eclass/semantic-release-npm-github-config, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/github@7.2.2
npm WARN node_modules/@semantic-release/github
npm WARN   dev @semantic-release/github@"7.2.2" from the root project
npm WARN   1 more (semantic-release)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: hubot-info-rut@4.0.5
npm WARN Found: semantic-release@17.4.2
npm WARN node_modules/semantic-release
npm WARN   dev semantic-release@"19.0.0" from the root project
npm WARN   7 more (@eclass/semantic-release-npm-github-config, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/npm@7.1.3
npm WARN node_modules/@semantic-release/npm
npm WARN   dev @semantic-release/npm@"7.1.3" from the root project
npm WARN   1 more (semantic-release)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: hubot-info-rut@4.0.5
npm ERR! Found: semantic-release@19.0.0
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"19.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/github@7.2.2
npm ERR! node_modules/@semantic-release/github
npm ERR!   dev @semantic-release/github@"7.2.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-03-07T10_04_39_857Z-debug-0.log

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