This page was not yet optimized for use on mobile devices.
CVE-2022-36799
Data ?
Vulnerability ID | CVE-2022-36799 |
---|---|
Published on | 01.08.2022 11:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:atlassian:jira_data_center:-:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_data_center:4.5.0:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_data_center:4.5.1:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_data_center:4.5.2:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_data_center:4.5.3:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_data_center:4.5.4:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_data_center:4.5.5:*:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_data_center:4.5.6:rc01:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_data_center:4.5.6:rc02:*:*:*:*:*:*,
cpe:2.3:a:atlassian:jira_data_center:4.6.0:*:*:*:*:*:*:*,
…
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.