[
https://issues.apache.org/jira/browse/SPARK-37630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495693#comment-17495693
]
Jason Crowder commented on SPARK-37630:
---------------------------------------
We're in the same boat as you. The upcoming 3.3 release resolves this
vulnerability issue, but we needed a fix right away. We found that we can use
the Log4j 1.x bridge to migrate over to the latest version of Log4j. All we had
to do is replace log4j-1.2.17.jar with the following files:
log4j-api-2.17.1.jar, log4j-core-2.17.1.jar, and log4j-1.2-api-2.17.1.jar. May
not work for everyone, but it worked for our use case.
> Security issue from Log4j 1.X exploit
> -------------------------------------
>
> Key: SPARK-37630
> URL: https://issues.apache.org/jira/browse/SPARK-37630
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.4.8, 3.2.0
> Reporter: Ismail H
> Priority: Major
> Labels: security
>
> log4j is being used in version [1.2.17|#L122]]
>
> This version has been deprecated and since [then have a known issue that
> hasn't been adressed in 1.X
> versions|https://www.cvedetails.com/cve/CVE-2019-17571/].
>
> *Solution:*
> * Upgrade log4j to version 2.15.0 which correct all known issues. [Last
> known issues |https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
