[
https://issues.apache.org/jira/browse/AVRO-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478115#comment-17478115
]
Ryan Skraba commented on AVRO-3304:
-----------------------------------
I did the alternate implementation (suggested by [~mgrigorov]) that drops in
*reload4j* [(https://reload4j.qos.ch/|https://reload4j.qos.ch/]) artifacts with
actual security fixes. This seems like a better mitigation since the
avro-tools jar will not bundle current (and future) known CVE.
I think the long-term solution is to adopt downstream projects that include
log4j2 security and performance improvements as soon as they are available (in
this case, Hadoop), _or_ alternatively modify the tool to only work with files
on the local filesystem.
> 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)
