This page was not yet optimized for use on mobile devices.
CVE-2018-5225
Data ?
Vulnerability ID | CVE-2018-5225 |
---|---|
Published on | 22.03.2018 13:29 |
Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:atlassian:bitbucket:4.13.0:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bitbucket:4.13.1:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bitbucket:4.14.0:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bitbucket:4.14.1:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bitbucket:4.14.2:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bitbucket:4.14.3:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bitbucket:4.14.4:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bitbucket:4.14.5:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bitbucket:4.14.6:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:bitbucket:4.14.7:*:*:*:*:*:*:*,
…
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.