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

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

                Author: ASF GitHub Bot
            Created on: 14/Dec/21 13:30
            Start Date: 14/Dec/21 13:30
    Worklog Time Spent: 10m 
      Work Description: dzou commented on pull request #16224:
URL: https://github.com/apache/beam/pull/16224#issuecomment-993540685


   @suztomo -- Sorry to disturb your vacation. I have one last question -- The 
team wants to upgrade the version of flogger in pubsublite from 0.7.1 to 0.7.2 
[due to the log4j 
concerns](https://github.com/google/flogger/releases/tag/flogger-0.7.2) even 
though log4j is not brought in directly.
   
   In this case, do you recommend doing a patch release of pubsublite to 
include this version upgrade? I.e. releasing a `pubsublite 1.2.1` that has the 
version upgrade? 
https://search.maven.org/artifact/com.google.cloud/google-cloud-pubsublite/1.2.0/jar


-- 
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: 695759)
    Time Spent: 10h 40m  (was: 10.5h)

> 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.35.0
>
>          Time Spent: 10h 40m
>  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.
>  
> [UPDATED]
> The vulnerability is labeled to `CVE-2021-44228`.
>  * [https://nvd.nist.gov/vuln/detail/CVE-2021-44228]
>  
> ## 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