msal-node using old jsonwebtoken npm pkg triggering npm audit issue - npm

we are using mssql npm package
it has dependency with like below:
mssql > tedious > #azure/identity > #azure/msal-node > jsonwebtoken
Now we are getting below audit error:
https://github.com/advisories/GHSA-27h2-hvpr-p74q
Any one already having this issue and know any workaround?

Related

1 high severity vulnerability Incorrect Comparison in axios when installing Nest

On installing nest, received warning
found 1 high severity vulnerability run npm audit fix to fix them, or npm audit for details
Result on npm audit
High Incorrect Comparison in axios
Package axios
Dependency of #nestjs/common
Path #nestjs/common > axios
More info https://github.com/advisories/GHSA-cph5-m8f7-6c5x
Why getting this issue and How to fix it ?
Tried npm audit fix but not solving the issue.
Thanks!
If you're using NPM 8: https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides
Or just upgrade #nestjs/common to its latest version (v8.2.6)
$ npm ls axios
myapp#0.0.1 /tmp/foo
└─┬ #nestjs/common#8.2.6
└── axios#0.24.0

How to fix Missing Origin Validation error for "webpack-dev-server" in npm

npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Missing Origin Validation
Package webpack-dev-server
Patched in >=3.1.6
Dependency of laravel-mix [dev]
Path laravel-mix > webpack-dev-server
More info https://nodesecurity.io/advisories/725
found 1 high severity vulnerability in 11710 scanned packages
1 vulnerability requires manual review. See the full report for details.
How to fix this i cannot use laravel
whenever i try run command "npm run dev" it shows several problem
This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.
I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.
If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.
Maybe you must wait to update laravel-mix.
Ref link: https://github.com/JeffreyWay/laravel-mix/issues/1809
Because version of webpack-dev-server < 3.1.6 in laravel-mix.
Quick solution:
Turning off npm audit on package installation
https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities

npm ERR! Unexpected end of JSON input while parsing near '...":{"shasum":"ae6c2edf'

npm ERR! Unexpected end of JSON input while parsing near '...":{"shasum":"ae6c2edf'
getting this error while npm install.
Steps i had done
1. create a new project
2. done npm install
getting this error for all new projects.
Cleaning the corrupted local npm cache may fix this error.
npm cache clean --force
Just run your npm command again after executing the above command in your terminal.
There could be few other reasons for the invalid JSON, as described in the official documentation here.
The official npm website has well documented most of the common errors. But unfortunately they don’t appear on the top results when you google the error.
updating angular cli to latest worked for me.

Not modify package.json when doing npm audit fix

I've updated my npm version, and I think npm audit is a new feature. When I run npm audit fix some of my packages versions are changed from package.json. I just want keep the packages as same as my coworkers
To answer the original question, if you really want to skip auditing completely when installing (for whatever reason, in my case I wanted to troubleshoot an exception when installing) you can use --no-audit flag:
npm install --no-audit
npm audit fix is not must to get your app up and running. I use this command when I want to make sure that there is no potential security vulnerability so that git hub won't have any object against my project. In case you still want to use audit fix without changing rest files, try this commands
Run audit fix without modifying node_modules, but still updating the pkglock:
$ npm audit fix --package-lock-only
Skip updating devDependencies:
$ npm audit fix --only=prod
Do a dry run to get an idea of what audit fix will do, and also output install information in JSON format:
$ npm audit fix --dry-run --json
Check out this link for your future reference:
https://docs.npmjs.com/cli/audit

Error for Angular5

Install the ng2-select-ex via npm package manager
npm i ng2-select-ex --save
Using this repo - https://optimistex.github.io/ng2-select-ex/ results following error: No provider for DomSanitizer!
Have you tried importing DomSanitizer?