This page was not yet optimized for use on mobile devices.
CVE-2021-4231
Data
| Vulnerability ID | CVE-2021-4231 |
|---|---|
| Published on | 26.05.2022 14:15 |
| Severity | MEDIUM |
Vulnerable configurations
- cpe:2.3:a:angular:angular:11.1.0:next0:*:*:*:node.js:*:*
- cpe:2.3:a:angular:angular:11.1.0:next1:*:*:*:node.js:*:*
- cpe:2.3:a:angular:angular:11.1.0:next2:*:*:*:node.js:*:*
-
cpe:2.3:a:angularjs:angularjs:-:*:*:*:*:*:*:*,
cpe:2.3:a:angularjs:angularjs:0.9.0:*:*:*:*:*:*:*,
cpe:2.3:a:angularjs:angularjs:0.9.1:*:*:*:*:*:*:*,
cpe:2.3:a:angularjs:angularjs:0.9.2:*:*:*:*:*:*:*,
cpe:2.3:a:angularjs:angularjs:0.9.3:*:*:*:*:*:*:*,
cpe:2.3:a:angularjs:angularjs:0.9.4:*:*:*:*:*:*:*,
cpe:2.3:a:angularjs:angularjs:0.9.5:*:*:*:*:*:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.