This page was not yet optimized for use on mobile devices.
CVE-2019-16728
Data ?
Vulnerability ID | CVE-2019-16728 |
---|---|
Published on | 24.09.2019 05:15 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:cure53:dompurify:-:*:*:*:*:*:*:*,
cpe:2.3:a:cure53:dompurify:0.1:*:*:*:*:*:*:*,
cpe:2.3:a:cure53:dompurify:0.3:*:*:*:*:*:*:*,
cpe:2.3:a:cure53:dompurify:0.4:*:*:*:*:*:*:*,
cpe:2.3:a:cure53:dompurify:0.4.2:*:*:*:*:*:*:*,
cpe:2.3:a:cure53:dompurify:0.4.3:*:*:*:*:*:*:*,
cpe:2.3:a:cure53:dompurify:0.4.4:*:*:*:*:*:*:*,
cpe:2.3:a:cure53:dompurify:0.4.5:*:*:*:*:*:*:*,
cpe:2.3:a:cure53:dompurify:0.6.0:*:*:*:*:*:*:*,
cpe:2.3:a:cure53:dompurify:0.6.1:*:*:*:*:*:*:*,
…
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.