You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "James Inlow (Jira)" <ji...@apache.org> on 2022/02/04 19:44:00 UTC

[jira] [Commented] (SPARK-37630) Security issue from Log4j 1.X exploit

    [ https://issues.apache.org/jira/browse/SPARK-37630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487271#comment-17487271 ] 

James Inlow commented on SPARK-37630:
-------------------------------------

How can we know about if Spark is impacted by any other more recent CVEs impacting log4j 1.x?

Specifically:
 *  [https://nvd.nist.gov/vuln/detail/CVE-2022-23307]
 * [https://nvd.nist.gov/vuln/detail/CVE-2022-23305]

Not sure the correct platform to ask these questions?

 

> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org