-
Notifications
You must be signed in to change notification settings - Fork 345
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
update mammoth version to avoid vuln #113
base: master
Are you sure you want to change the base?
Conversation
Vulnerable Package: mime More Information: Please consider upgrading mime to prevent deploying vulnerable code into production. For more information, visit: https://nvd.nist.gov/vuln/detail/CVE-2017-16138, or visit the FAQ |
Vulnerable Package: lodash More Information: Please consider upgrading lodash to prevent deploying vulnerable code into production. For more information, visit: https://nvd.nist.gov/vuln/detail/CVE-2018-3721, or visit the FAQ |
Vulnerable Package: webpack-dev-server More Information: Please consider upgrading webpack-dev-server to prevent deploying vulnerable code into production. For more information, visit: https://nvd.nist.gov/vuln/detail/CVE-2018-14732, or visit the FAQ |
Vulnerable Package: lodash More Information: Please consider upgrading lodash to prevent deploying vulnerable code into production. For more information, visit: https://nvd.nist.gov/vuln/detail/CVE-2018-16487, or visit the FAQ |
Vulnerable Package: tar More Information: Please consider upgrading tar to prevent deploying vulnerable code into production. For more information, visit: https://nvd.nist.gov/vuln/detail/CVE-2018-20834, or visit the FAQ |
Vulnerable Package: fstream More Information: Please consider upgrading fstream to prevent deploying vulnerable code into production. For more information, visit: npm/fstream@6a77d2f, or visit the FAQ |
Vulnerable Package: js-yaml More Information: Please consider upgrading js-yaml to prevent deploying vulnerable code into production. For more information, visit: nodeca/js-yaml#480, or visit the FAQ |
Vulnerable Package: js-yaml More Information: Please consider upgrading js-yaml to prevent deploying vulnerable code into production. For more information, visit: nodeca/js-yaml#475, or visit the FAQ |
Vulnerable Package: braces More Information: Please consider upgrading braces to prevent deploying vulnerable code into production. For more information, visit: micromatch/braces@abdafb0, or visit the FAQ |
Vulnerable Package: eslint More Information: Please consider upgrading eslint to prevent deploying vulnerable code into production. For more information, visit: eslint/eslint@f6901d0, or visit the FAQ |
Vulnerable Package: mem More Information: Please consider upgrading mem to prevent deploying vulnerable code into production. For more information, visit: sindresorhus/memoize@da4e439, or visit the FAQ |
Vulnerable Package: lodash More Information: Please consider upgrading lodash to prevent deploying vulnerable code into production. For more information, visit: lodash/lodash#4336, or visit the FAQ |
Vulnerable Package: lodash.mergewith More Information: Please consider upgrading lodash.mergewith to prevent deploying vulnerable code into production. For more information, visit: lodash/lodash#4336, or visit the FAQ |
Vulnerable Package: handlebars More Information: Please consider upgrading handlebars to prevent deploying vulnerable code into production. For more information, visit: handlebars-lang/handlebars.js@v4.1.1...v4.1.2, or visit the FAQ |
Vulnerable Package: lodash More Information: Please consider upgrading lodash to prevent deploying vulnerable code into production. For more information, visit: https://nvd.nist.gov/vuln/detail/CVE-2019-1010266, or visit the FAQ |
Vulnerable Package: mixin-deep More Information: Please consider upgrading mixin-deep to prevent deploying vulnerable code into production. For more information, visit: https://nvd.nist.gov/vuln/detail/CVE-2019-10746, or visit the FAQ |
Vulnerable Package: set-value More Information: Please consider upgrading set-value to prevent deploying vulnerable code into production. For more information, visit: https://nvd.nist.gov/vuln/detail/CVE-2019-10747, or visit the FAQ |
mammoth 1.3.6 uses an vulnerable version of xmlbuilder (via lodash). This updates it to a non-vulnerable version.
Issue: #112