You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Aviral Sinha (Jira)" <ji...@apache.org> on 2026/02/09 08:14:00 UTC

[jira] [Commented] (SOLR-18097) Log4j Upgrade: 2.17.2 → 2.25.3 (CVE-2025-68161 Remediation) Confirmation on remediation

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

Aviral Sinha commented on SOLR-18097:
-------------------------------------

Hi [~dsmiley], could you please let us know if our understanding is correct?

> Log4j Upgrade: 2.17.2 → 2.25.3 (CVE-2025-68161 Remediation) Confirmation on remediation
> ---------------------------------------------------------------------------------------
>
>                 Key: SOLR-18097
>                 URL: https://issues.apache.org/jira/browse/SOLR-18097
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>    Affects Versions: 8.4
>            Reporter: Aviral Sinha
>            Priority: Blocker
>
> _*Given that we do not utilize socket appenders or any network-based logging mechanisms, we believe that vulnerabilities specifically targeting the transmission of logs over the network (such as those requiring a Socket Appender to be active) are not applicable to our current architecure.*_
>  
> Could you please confirm if our assessment is correct? Specifically, we want to ensure that in the absence of a declared Socket Appender, the risk of exploitation is mitigated.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org