Text of github.com › jenkinsci › jenkins › issues › 25584 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

[JENKINS-67353] log4j CVE-2021-44228 and CVE-2021-45046 in Jenkins · Issue #25584 · jenkinsci/jenkins · GitHub

Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert [JENKINS-67353] log4j CVE-2021-44228 and CVE-2021-45046 in Jenkins #25584 New issue Copy link New issue Copy link Open Epic 1 / 1 1 of 1 issue completed Open [JENKINS-67353] log4j CVE-2021-44228 and CVE-2021-45046 in Jenkins #25584 Epic 1 / 1 1 of 1 issue completed Copy link Labels component:other imported-jira-issue priority:critical resolution:unresolved security Description jenkins-infra-bot opened on Dec 10, 2021 Issue body actions Tracking the status of the critical severity log4j RCE vulnerability CVE-2021-44228 (fixed in 2.15.0), as well as the Low severity vulnerability CVE-2021-45046 (fixed in 2.16.0).

The following plugins are known to include vulnerable releases of log4j 2.x as of Dec 10, or have included vulnerable releases of log4j 2.x in the past: Plugin CVE-2021-44228 CVE-2021-45046 https://plugins.jenkins.io/audit-log JENKINS-67355 "> JENKINS-67355 updated to 2.16.0 in 1.3 Same https://plugins.jenkins.io/bootstraped-multi-test-results-report updated to 2.17.0 in 2.2.1 Same https://plugins.jenkins.io/checkmarx JENKINS-67356 "> JENKINS-67356 updated to 2.16.0 in 2021.4.3 Same https://plugins.jenkins.io/cmakebuilder log4j 2.x only present in 2.6.1 (obsolete since mid 2019) Same https://plugins.jenkins.io/cucumber-reports log4j 2.x only present in 1.1.0 through 3.16.0 (both inclusive), obsolete since mid 2018 Same https://plugins.jenkins.io/hp-application-automation-tools-plugin JENKINS-67357 "> JENKINS-67357 updated to 2.17.0 in 7.2 Same https://plugins.jenkins.io/lambdatest-automation JENKINS-67358 "> JENKINS-67358 Log4j fully removed in 1.20.0 Same https://plugins.jenkins.io/peass-ci #71 updated to 2.15.0 in 2.0.0-540.v244012ecda48 #73 updated to 2.17.0 in 2.0.0-576.vbc3d83ca3c4a https://plugins.jenkins.io/pipeline-huaweicloud-plugin JENKINS-67359 "> JENKINS-67359 no fix as of 0.0.1 Also tracked in JENKINS-67359 "> JENKINS-67359 https://plugins.jenkins.io/reliza-integration updated to 2.15.0 in 0.1.14 Updated to 2.17.0 in 0.1.15 https://plugins.jenkins.io/semantic-versioning-plugin log4j 2.x only present in 1.0 through 1.3 (both inclusive), obsolete since mid 2014 Same https://plugins.jenkins.io/talend JENKINS-67360 "> JENKINS-67360 updated to 2.15.0 in 1.3-rc42.f3ec422d618b JENKINS-67369 "> JENKINS-67369 log4j removed from 1.4-rc43.dbb2c0671f67 https://plugins.jenkins.io/testdroid-run-in-cloud JENKINS-67361 "> JENKINS-67361 Updated to 2.17.2 in 3.22.4 Same https://plugins.jenkins.io/thundra-foresight #5 fixed as of 13.v84a42ba15ff7 Same https://plugins.jenkins.io/venafi-vcert #9 no fix as of 2.0.0 Also tracked in #9 https://plugins.jenkins.io/xray-connector #53 updated to 2.16.0 in 2.5.2.1 Same Some references: https://www.lunasec.io/docs/blog/log4j-zero-day/ https://logging.apache.org/log4j/2.x/security.html Restrict LDAP access via JNDI apache/logging-log4j2#608 has some useful discussion about scope and workarounds https://www.jenkins.io/blog/2021/12/10/log4j2-rce-CVE-2021-44228/ our blog post https://github.com/issues?q=org%3Ajenkinsci+CVE-2021-44228 related issues and PRs on GitHub Summary of what we know so far: The vulnerability CVE-2021-44228 affects log4j 2.x only .

It was introduced in version 2.0-beta9 and fixed in 2.15.0-rc2 . log4j 1.x is unaffected. For the vulnerability to be present, log4j-core-2.*.jar (or a shaded equivalent) needs to be bundled with the plugin, anything else (slf4j bridges, API jars, log4j 1.x) doesn't include the vulnerable class (see below). Recent JREs prohibit the specific LDAP RCE exploit, but other exploits exist (e.g. capturing env vars). Maven Shade Plugin may rename packages, so there may be matches in other packages (but a patched usage-in-plugins found none in latest plugin releases) Further plugins may have included the library in older releases.

We are working on a list. log4j 2.16.0 includes a fix for another security vulnerability , see https://lists.apache.org/thread/83y7dx5xvn3h5290q1twn16tltolv88f It's low severity, and requires a nondefault configuration to be exploitable (or attackers able to configure logging). It affects 2.0-beta9 through 2.15.0 (inclusive) and is fixed in 2.16.0 . The specific affected classes are org.apache.logging.log4j.core.lookup.JndiLookup and org.apache.logging.log4j.core.net.JndiManager (previously org.apache.logging.log4j.core.appender.JndiManager ).

The former should be removed manually according to https://logging.apache.org/log4j/2.x/security.html when using affected versions. This applied to both vulnerabilities. Originally reported by danielbeck , imported from: log4j CVE-2021-44228 and CVE-2021-45046 in Jenkins status : Open priority : Critical component(s) : other label(s) : CVE-2021-44228 , CVE-2021-45046 , jcabot:001, jcabot:002, security resolution : Unresolved votes : 1 watchers : 19 imported : 2025-12-08 Raw content of original issue Tracking the status of the critical severity log4j RCE vulnerability CVE-2021-44228 (fixed in 2.15.0), as well as the Low severity vulnerability CVE-2021-45046 (fixed in 2.16.0).

The following plugins are known to include vulnerable releases of log4j 2.x as of Dec 10, or have included vulnerable releases of log4j 2.x in the past: Plugin CVE-2021-44228 CVE-2021-45046 https://plugins.jenkins.io/audit-log JENKINS-67355 updated to 2.16.0 in 1.3 Same https://plugins.jenkins.io/bootstraped-multi-test-results-report updated to 2.17.0 in 2.2.1 Same https://plugins.jenkins.io/checkmarx JENKINS-67356 updated to 2.16.0 in 2021.4.3 Same https://plugins.jenkins.io/cmakebuilder log4j 2.x only present in 2.6.1 (obsolete since mid 2019) Same https://plugins.jenkins.io/cucumber-reports log4j 2.x only present in 1.1.0 through 3.16.0 (both inclusive), obsolete since mid 2018 Same https://plugins.jenkins.io/hp-application-automation-tools-plugin JENKINS-67357 updated to 2.17.0 in 7.2 Same https://plugins.jenkins.io/lambdatest-automation JENKINS-67358 Log4j fully removed in 1.20.0 Same https://plugins.jenkins.io/peass-ci #71 updated to 2.15.0 in 2.0.0-540.v244012ecda48 #73 updated to 2.17.0 in 2.0.0-576.vbc3d83ca3c4a https://plugins.jenkins.io/pipeline-huaweicloud-plugin JENKINS-67359 no fix as of 0.0.1 Also tracked in JENKINS-67359 https://plugins.jenkins.io/reliza-integration updated to 2.15.0 in 0.1.14 Updated to 2.17.0 in 0.1.15 https://plugins.jenkins.io/semantic-versioning-plugin log4j 2.x only present in 1.0 through 1.3 (both inclusive), obsolete since mid 2014 Same https://plugins.jenkins.io/talend JENKINS-67360 updated to 2.15.0 in 1.3-rc42.f3ec422d618b JENKINS-67369 log4j removed from 1.4-rc43.dbb2c0671f67 https://plugins.jenkins.io/testdroid-run-in-cloud JENKINS-67361 Updated to 2.17.2 in 3.22.4 Same https://plugins.jenkins.io/thundra-foresight #5 fixed as of 13.v84a42ba15ff7 Same https://plugins.jenkins.io/venafi-vcert #9 no fix as of 2.0.0 Also tracked in #9 https://plugins.jenkins.io/xray-connector #53 updated to 2.16.0 in 2.5.2.1 Same Some references: https://www.lunasec.io/docs/blog/log4j-zero-day/ https://logging.apache.org/log4j/2.x/security.html Restrict LDAP access via JNDI apache/logging-log4j2#608 has some useful discussion about scope and workarounds https://www.jenkins.io/blog/2021/12/10/log4j2-rce-CVE-2021-44228/ our blog post https://github.com/issues?q=org%3Ajenkinsci+CVE-2021-44228 related issues and PRs on GitHub Summary of what we know so far: The vulnerability CVE-2021-44228 affects log4j 2.x only .

It was introduced in version 2.0-beta9 and fixed in 2.15.0-rc2 . log4j 1.x is unaffected. For the vulnerability to be present, log4j-core-2.*.jar (or a shaded equivalent) needs to be bundled with the plugin, anything else (slf4j bridges, API jars, log4j 1.x) doesn't include the vulnerable class (see below). Recent JREs prohibit the specific LDAP RCE exp

The rest of this page is on the live site.