12/25/2023 0 Comments Splunk log4j vulnerability![]() ![]() Some on-premises products use an Atlassian-maintained fork of Log4j 1.2.17, which is not vulnerable to CVE-2021-44228. Our Security team investigated the impact of the Log4j remote code execution vulnerability (CVE-2021-44228) and have determined that no Atlassian on-premises products are vulnerable to CVE-2021-44228. Is my on-premises Server/Data Center instance affected? This vulnerability has been mitigated for all Atlassian cloud products previously using vulnerable versions of Log4j. To date, our analysis has not identified compromise of Atlassian systems or customer data prior to the patching of these systems. No, Atlassian customers are not vulnerable, and no action is required. In addition, we have guidance about the related vulnerabilities, CVE-2021-45046 and CVE-2021-45105. This page contains frequently asked questions and answers about our recently published security advisory Multiple Products Security Advisory - Log4j Vulnerable To Remote Code Execution - CVE-2021-44228 related to the vulnerability affecting Log4j, CVE-2021-44228. Attachment health check shows warning message when a custom attachment page is used.Cannot start Jira over another node via pbrun command. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |