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

Posted to oak-issues@jackrabbit.apache.org by "Nitin Gupta (Jira)" <ji...@apache.org> on 2022/01/12 04:01:00 UTC

[jira] [Comment Edited] (OAK-9661) Upgrade Solr to v8.11.1

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

Nitin Gupta edited comment on OAK-9661 at 1/12/22, 4:00 AM:
------------------------------------------------------------

trunk - [https://github.com/apache/jackrabbit-oak/commit/6be355c80cc2c2aea1b66ece0b4c522bf2eb7d2d] 

 

1.22 - [https://github.com/apache/jackrabbit-oak/commit/1a17472a470d447f596ba344e7227c8a45db76e5] 


was (Author: nitigup):
trunk - [https://github.com/apache/jackrabbit-oak/commit/6be355c80cc2c2aea1b66ece0b4c522bf2eb7d2d] 

> Upgrade Solr to v8.11.1
> -----------------------
>
>                 Key: OAK-9661
>                 URL: https://issues.apache.org/jira/browse/OAK-9661
>             Project: Jackrabbit Oak
>          Issue Type: Task
>            Reporter: Nitin Gupta
>            Assignee: Nitin Gupta
>            Priority: Major
>              Labels: candidate_oak_1_22, candidate_oak_1_6, candidate_oak_1_8
>             Fix For: 1.44.0
>
>
> To fix log4j vulnerability. Details [https://solr.apache.org/security.html#apache-solr-affected-by-apache-log4j-cve-2021-44228]
>  
> This update is just to make explanation around this easier - but since we are no longer using embedded solr - oak should not be impacted by the log4j vulnerability due to the solr dependency. 



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