@azure/msal-node vulnerabilities
Microsoft Authentication Library for Node
- Registry
- npm
- Latest
- 7.2.2
- License
- MIT
2 known advisories
The latest version, 7.2.2, is not affected by any of them. Projects on older versions may be.
npm install @azure/msal-node@7.2.2Is your project on an affected @azure/msal-node?
Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for @azure/msal-node
MSAL Node authorization code flow may disclose parameters to an attacker-controlled endpoint
- Affected
- >=5.0.0-beta.0 <7.1.0
- Fixed in
- 7.1.0
Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability
- Affected
- >=2.7.0 <2.9.2
- Fixed in
- 2.9.2
Is your @azure/msal-node version vulnerable?
- @azure/msal-node 7.2No known advisories in 7.2.2
- @azure/msal-node 7.1No known advisories in 7.1.2
- @azure/msal-node 7.01 advisory in 7.0.2
- @azure/msal-node 6.01 advisory in 6.0.1
- @azure/msal-node 5.61 advisory in 5.6.0
- @azure/msal-node 5.51 advisory in 5.5.0
- @azure/msal-node 5.41 advisory in 5.4.3
- @azure/msal-node 5.31 advisory in 5.3.1
- @azure/msal-node 5.21 advisory in 5.2.5
- @azure/msal-node 5.11 advisory in 5.1.5
Which of your client projects still run an old @azure/msal-node?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.