{"affected":[{"ecosystem_specific":{"binaries":[{"disruptor":"3.4.4-lp152.2.3.1","disruptor-javadoc":"3.4.4-lp152.2.3.1","jakarta-servlet":"5.0.0-lp152.2.1","jakarta-servlet-javadoc":"5.0.0-lp152.2.1","log4j":"2.16.0-lp152.3.9.1","log4j-javadoc":"2.16.0-lp152.3.9.1","log4j-jcl":"2.16.0-lp152.3.9.1","log4j-slf4j":"2.16.0-lp152.3.9.1"}]},"package":{"ecosystem":"openSUSE:Leap 15.2","name":"disruptor","purl":"purl:rpm/suse/disruptor&distro=openSUSE%20Leap%2015.2"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"3.4.4-lp152.2.3.1"}],"type":"ECOSYSTEM"}]},{"ecosystem_specific":{"binaries":[{"disruptor":"3.4.4-lp152.2.3.1","disruptor-javadoc":"3.4.4-lp152.2.3.1","jakarta-servlet":"5.0.0-lp152.2.1","jakarta-servlet-javadoc":"5.0.0-lp152.2.1","log4j":"2.16.0-lp152.3.9.1","log4j-javadoc":"2.16.0-lp152.3.9.1","log4j-jcl":"2.16.0-lp152.3.9.1","log4j-slf4j":"2.16.0-lp152.3.9.1"}]},"package":{"ecosystem":"openSUSE:Leap 15.2","name":"jakarta-servlet","purl":"purl:rpm/suse/jakarta-servlet&distro=openSUSE%20Leap%2015.2"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"5.0.0-lp152.2.1"}],"type":"ECOSYSTEM"}]},{"ecosystem_specific":{"binaries":[{"disruptor":"3.4.4-lp152.2.3.1","disruptor-javadoc":"3.4.4-lp152.2.3.1","jakarta-servlet":"5.0.0-lp152.2.1","jakarta-servlet-javadoc":"5.0.0-lp152.2.1","log4j":"2.16.0-lp152.3.9.1","log4j-javadoc":"2.16.0-lp152.3.9.1","log4j-jcl":"2.16.0-lp152.3.9.1","log4j-slf4j":"2.16.0-lp152.3.9.1"}]},"package":{"ecosystem":"openSUSE:Leap 15.2","name":"log4j","purl":"purl:rpm/suse/log4j&distro=openSUSE%20Leap%2015.2"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"2.16.0-lp152.3.9.1"}],"type":"ECOSYSTEM"}]}],"aliases":[],"details":"This update for log4j fixes the following issue:\n\n- Previously published fixes for log4jshell turned out to be incomplete.\n  Upstream has followed up on the original patch for CVE-2021-44228 with\n  several additional changes (LOG4J2-3198, LOG4J2-3201, LOG4J2-3208, and\n  LOG4J2-3211) that are included in this update. Since the totality of\n  those patches is pretty much equivalent to an update to the latest\n  version of log4j, we did update the package's tarball from version\n  2.13.0 to 2.16.0 instead of trying to apply those patches to the old\n  version. This change brings in a new dependency on 'jakarta-servlet'\n  and a version update of 'disruptor'. [bsc#1193743, CVE-2021-45046]\n\nThis update was imported from SUSE:SLE-15-SP2:Update.\n","id":"openSUSE-SU-2021:1601-1","modified":"2021-12-20T09:16:57Z","published":"2021-12-20T09:16:57Z","references":[{"type":"ADVISORY","url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/YLSFAYMV5DOWQ3EO5252SX7QTCHNCWGK/"},{"type":"REPORT","url":"https://bugzilla.suse.com/1193743"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2021-44228"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2021-45046"}],"related":["CVE-2021-44228","CVE-2021-45046"],"summary":"Security update for log4j"}