This page was not yet optimized for use on mobile devices.
CVE-2018-5224
Data ?
Vulnerability ID | CVE-2018-5224 |
---|---|
Published on | 29.03.2018 13:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:atlassian:bamboo:2.7.1:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bamboo:2.7.2:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bamboo:2.7.3:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bamboo:2.7.4:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bamboo:3.0:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bamboo:3.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bamboo:3.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bamboo:3.0.3:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bamboo:3.1:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bamboo:3.1.1:*:*:*:*:*:*:*,
…
running on/with
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.