ua-parser-js vulnerabilities
Detect Browser, Engine, OS, CPU, and Device type/model from User-Agent & Client Hints data. Supports browser & node.js environment
- Registry
- npm
- Latest
- 2.0.10
- License
- AGPL-3.0-or-later
6 known advisories
The latest version, 2.0.10, is not affected by any of them. Projects on older versions may be.
npm install ua-parser-js@2.0.10Security advisories for ua-parser-js
UAParser.js: Unbounded `Sec-CH-UA-Model` parsing can trigger ReDoS in `withClientHints()`
- Affected
- >=2.0.1 <2.0.10
- Fixed in
- 2.0.10
ReDoS Vulnerability in ua-parser-js version
- Affected
- >=0.7.30 <0.7.33 · >=0.8.0 <1.0.33
- Fixed in
- 0.7.33, 1.0.33
ua-parser-js Regular Expression Denial of Service vulnerability
- Affected
- <0.7.23
- Fixed in
- 0.7.23
Embedded malware in ua-parser-js
- Affected
- >=0.7.29 <0.7.30 · >=0.8.0 <0.8.1 · >=1.0.0 <1.0.1
- Fixed in
- 0.7.30, 0.8.1, 1.0.1
Regular Expression Denial of Service in ua-parser-js
- Affected
- <0.7.22
- Fixed in
- 0.7.22
Regular Expression Denial of Service (ReDoS) in ua-parser-js
- Affected
- >=0.7.14 <0.7.24
- Fixed in
- 0.7.24
Which of your client projects still run an old ua-parser-js?
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.