/
CVE-2021-44228 Log4j Vulnerable To Remote Code Execution

CVE-2021-44228 Log4j Vulnerable To Remote Code Execution

Release Date

Dec 22, 2021

CVE ID

CVE-2021-44228

We do not include our own log4j in our apps. The logging is done by the logging functionality provided by Atlassian.

This means: Our apps would only be affected by the log4j vulnarability if Jira/Confluence was. This - according to Atlassian - is not the case. You can find more information about this in this FAQ: https://confluence.atlassian.com/security/multiple-products-security-advisory-log4j-vulnerable-to-remote-code-execution-cve-2021-44228-1103069934.html

We have not implemented the configuration described there: Developer Documentation - Using your own log4j configuration for your plugin . We think apps that have followed this documentation may cause problems.

 

Related content

How-to fix /auditing/view returns 500 Error Page
How-to fix /auditing/view returns 500 Error Page
More like this
Rest API - Metadata for Jira 4.7 pre-rendered
Rest API - Metadata for Jira 4.7 pre-rendered
More like this
Precondition - Application Link
Precondition - Application Link
More like this
Rest API - Metadata for Jira 5.3 pre-rendered
Rest API - Metadata for Jira 5.3 pre-rendered
More like this
Rest API - Metadata for Jira 5.1 pre-rendered
Rest API - Metadata for Jira 5.1 pre-rendered
More like this
Rest API - Metadata for Jira 5.2 pre-rendered
Rest API - Metadata for Jira 5.2 pre-rendered
More like this