Skip to content

[Snyk] Upgrade xmldom from 0.1.19 to 0.6.0#504

Open
snyk-bot wants to merge 1 commit into
v2.1.4from
snyk-upgrade-31b93cc078d33db14ad84374b846c193
Open

[Snyk] Upgrade xmldom from 0.1.19 to 0.6.0#504
snyk-bot wants to merge 1 commit into
v2.1.4from
snyk-upgrade-31b93cc078d33db14ad84374b846c193

Conversation

@snyk-bot
Copy link
Copy Markdown

Snyk has created this PR to upgrade xmldom from 0.1.19 to 0.6.0.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 16 versions ahead of your current version.
  • The recommended version was released 9 months ago, on 2021-04-17.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
XML External Entity (XXE) Injection
SNYK-JS-XMLDOM-1084960
484/1000
Why? Has a fix available, CVSS 5.4
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: xmldom
  • 0.6.0 - 2021-04-17
  • 0.5.0 - 2021-03-09
  • 0.4.0 - 2020-10-27
  • 0.3.0 - 2020-03-04
  • 0.2.1 - 2019-12-20
  • 0.2.0 - 2019-12-20
  • 0.1.31 - 2019-12-19
  • 0.1.30 - 2019-12-19
  • 0.1.29 - 2019-12-19
  • 0.1.27 - 2016-11-28
  • 0.1.26 - 2016-11-28
  • 0.1.25 - 2016-11-28
  • 0.1.24 - 2016-11-27
  • 0.1.22 - 2016-01-30
  • 0.1.21 - 2016-01-13
  • 0.1.20 - 2016-01-10
  • 0.1.19 - 2014-01-28
from xmldom GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@kaltura-hooks
Copy link
Copy Markdown

Hi @snyk-bot,
Thank you for contributing this pull request!
Please sign the Kaltura CLA so we can review and merge your contribution.
Learn more at http://bit.ly/KalturaContrib

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants