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

ASF GitHub Bot logged work on AVRO-3304:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Jan/22 18:27
            Start Date: 18/Jan/22 18:27
    Worklog Time Spent: 10m 
      Work Description: RyanSkraba opened a new pull request #1464:
URL: https://github.com/apache/avro/pull/1464


   This is an alternative to https://github.com/apache/avro/pull/1458
   
   That PR replaces the logging behind slf4j from log4j 1.x to slf4j-simple, 
while this PR drops in the reload4j replacement.
   
   Both these solutions are "mitigation" solutions for current CVEs, while 
downstream projects still bring in log4j 1.x dependencies. 
   
   I've verified that the classes in the generated avro-tools uberjar are the 
reload4j replacements.
   
   ### Jira
   
   - [X] My PR addresses the following [Avro 
Jira](https://issues.apache.org/jira/browse/AVRO/) issues and references them 
in the PR title. For example, "AVRO-1234: My Avro PR"
     - https://issues.apache.org/jira/browse/AVRO-3304
     - In case you are adding a dependency, check if the license complies with 
the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   
   ### Tests
   
   - [X] My PR does not need testing for this extremely good reason: the 
equivalent of a version bump.
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines. In 
addition, my commits follow the guidelines from "[How to write a good git 
commit message](https://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes 
how to use it.
     - All the public functions and the classes in the PR contain Javadoc that 
explain what it does
   


-- 
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: 710733)
    Time Spent: 1h 10m  (was: 1h)

> avro-tools Update log4j dependency for critical vulnerability
> -------------------------------------------------------------
>
>                 Key: AVRO-3304
>                 URL: https://issues.apache.org/jira/browse/AVRO-3304
>             Project: Apache Avro
>          Issue Type: Task
>          Components: tools
>    Affects Versions: 1.11.0
>            Reporter: Daniel Nash
>            Assignee: Ryan Skraba
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Our company security is having a fit because Nessus scans are triggering on 
> the bundled log4j in the avro-tools.jar.  Please update the log4j 
> dependencies to the latest versions to remove the critical vulnerability 
> present in the currently bundled log4j.



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

Reply via email to