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

Posted to dev@felix.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2021/12/16 05:55:00 UTC

[jira] [Commented] (FELIX-6485) Prepare a public statement w.r.t Log4Shell's impact on Felix

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

Carsten Ziegeler commented on FELIX-6485:
-----------------------------------------

I did a first pass and scanning the felix-dev git repo; I couldn't find any reference to a vulnerable log4j version being used

> Prepare a public statement w.r.t Log4Shell's impact on Felix
> ------------------------------------------------------------
>
>                 Key: FELIX-6485
>                 URL: https://issues.apache.org/jira/browse/FELIX-6485
>             Project: Felix
>          Issue Type: Task
>            Reporter: Nitin Gupta
>            Priority: Critical
>
> We need to assess what all felix modules and what versions of those are impacted (if they are, and how) by Log4Shell ([https://nvd.nist.gov/vuln/detail/CVE-2021-44228).]
>  
> It would be good to put out a public statement on the project page to state what all versions are not impacted and any mitigation (if needed) in case of versions that are impacted.



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