[ 
https://issues.apache.org/jira/browse/BEAM-13434?focusedWorklogId=694491&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-694491
 ]

ASF GitHub Bot logged work on BEAM-13434:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Dec/21 22:54
            Start Date: 11/Dec/21 22:54
    Worklog Time Spent: 10m 
      Work Description: aaltay commented on pull request #16191:
URL: https://github.com/apache/beam/pull/16191#issuecomment-991800679


   Given the severity of this issue, I am revising my position. I think it 
would good to CP this into 2.35.0. This would make it plenty clear based on 
beam source code analysis of the repo that 2.35.0 does not use the older log4j 
versions. And security scanner might catch this and mark this Beam version as 
impacted even if it is only limited to tests.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 694491)
    Time Spent: 2.5h  (was: 2h 20m)

> Bump up Apache log4j2 to 2.15.0 due to the vulnerability
> --------------------------------------------------------
>
>                 Key: BEAM-13434
>                 URL: https://issues.apache.org/jira/browse/BEAM-13434
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>    Affects Versions: 2.34.0
>            Reporter: Yu Ishikawa
>            Priority: P1
>             Fix For: 2.36.0
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> ## Overview
> 2.0 <= Apache log4j2 <= 2.14.1 has vulnerability.
>  
> >  In most cases, developers may write error messages caused by user input 
> > into the log. Attackers can use this feature to construct special data 
> > request packets through this vulnerability, and ultimately trigger remote 
> > code execution.
>  
> ## References
>  * 
> [https://www.cyberkendra.com/2021/12/worst-log4j-rce-zeroday-dropped-on.html]
>  * 
> https://www.spigotmc.org/threads/spigot-security-releases-%E2%80%94-1-8-8%E2%80%931-18.537204/



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to