This page was not yet optimized for use on mobile devices.
CVE-2017-18102
Data ?
Vulnerability ID | CVE-2017-18102 |
---|---|
Published on | 17.04.2018 13:29 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:atlassian:jira_server:7.5.0:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_server:7.5.1:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_server:7.5.2:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_server:7.5.3:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_server:7.5.4:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_server:7.6:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_server:7.6.0:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_server:7.6.1:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_server:7.6.2:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_server:7.6.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.