This page was not yet optimized for use on mobile devices.
CVE-2018-13395
Data ?
Vulnerability ID | CVE-2018-13395 |
---|---|
Published on | 28.08.2018 12:29 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:atlassian:jira:-:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira:2.1:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira:2.1:*:enterprise:*:*:*:*:*,
cpe:2.3:a:atlassian:jira:2.1:*:professional:*:*:*:*:*,
cpe:2.3:a:atlassian:jira:2.1:*:standard:*:*:*:*:*,
cpe:2.3:a:atlassian:jira:2.2:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira:2.2:*:enterprise:*:*:*:*:*,
cpe:2.3:a:atlassian:jira:2.2:*:professional:*:*:*:*:*,
cpe:2.3:a:atlassian:jira:2.2:*:standard:*:*:*:*:*,
cpe:2.3:a:atlassian:jira:2.2.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.