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

Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2021/12/16 21:10:00 UTC

[jira] [Resolved] (SLING-11002) Prepare a public statement w.r.t Log4Shell's impact on sling

     [ https://issues.apache.org/jira/browse/SLING-11002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu resolved SLING-11002.
-------------------------------------
    Resolution: Done

The official Apache Sling statement is at https://sling.apache.org/security/log4shell.html . Thanks for raising this [~ngupta]

> Prepare a public statement w.r.t Log4Shell's impact on sling
> ------------------------------------------------------------
>
>                 Key: SLING-11002
>                 URL: https://issues.apache.org/jira/browse/SLING-11002
>             Project: Sling
>          Issue Type: Task
>            Reporter: Nitin Gupta
>            Priority: Critical
>
> We need to assess what all sling modules and what possible versions 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)