This page was not yet optimized for use on mobile devices.
CVE-2019-5427
Data ?
Vulnerability ID | CVE-2019-5427 |
---|---|
Published on | 22.04.2019 21:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:mchange:c3p0:0.8.4:*:*:*:*:*:*:*,
cpe:2.3:a:mchange:c3p0:0.8.4.1:*:*:*:*:*:*:*,
cpe:2.3:a:mchange:c3p0:0.8.4.2:*:*:*:*:*:*:*,
cpe:2.3:a:mchange:c3p0:0.8.4.5:*:*:*:*:*:*:*,
cpe:2.3:a:mchange:c3p0:0.8.5:*:*:*:*:*:*:*,
cpe:2.3:a:mchange:c3p0:0.8.5.1:*:*:*:*:*:*:*,
cpe:2.3:a:mchange:c3p0:0.8.5.2:*:*:*:*:*:*:*,
cpe:2.3:a:mchange:c3p0:0.9.0:*:*:*:*:*:*:*,
cpe:2.3:a:mchange:c3p0:0.9.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:mchange:c3p0:0.9.0.3:*:*:*:*:*:*:*,
…
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.