Skip to content

chore(deps): update dependency marked to v2 [security] #3001

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

Merged
merged 1 commit into from
Feb 12, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 9, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
marked (source) ^1.2.9 -> ^2.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?

markedjs/marked#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:


Release Notes

markedjs/marked

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.

Renovate configuration

📅 Schedule: "" (UTC).

🚦 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 WhiteSource Renovate. View repository job log here.

@renovate renovate bot requested review from hiroppy and knagaitsev as code owners February 9, 2021 15:39
@renovate renovate bot added the renovate label Feb 9, 2021
@renovate renovate bot force-pushed the renovate/npm-marked-vulnerability branch from 0f1a05b to 5a6fef2 Compare February 9, 2021 15:43
@codecov
Copy link

codecov bot commented Feb 9, 2021

Codecov Report

Merging #3001 (08b7f7a) into master (4f1fec5) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #3001   +/-   ##
=======================================
  Coverage   92.39%   92.39%           
=======================================
  Files          37       37           
  Lines        1262     1262           
  Branches      326      326           
=======================================
  Hits         1166     1166           
  Misses         91       91           
  Partials        5        5           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4f1fec5...24eb39d. Read the comment docs.

@renovate renovate bot force-pushed the renovate/npm-marked-vulnerability branch from 5a6fef2 to 860f245 Compare February 11, 2021 19:04
@renovate renovate bot force-pushed the renovate/npm-marked-vulnerability branch from 860f245 to 24eb39d Compare February 12, 2021 10:38
@alexander-akait alexander-akait merged commit b0868c3 into master Feb 12, 2021
@alexander-akait alexander-akait deleted the renovate/npm-marked-vulnerability branch February 12, 2021 11:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants