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

Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2015/11/12 16:08:11 UTC

[jira] [Assigned] (SLING-5288) Restrict which classes can be deserialized

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

Bertrand Delacretaz reassigned SLING-5288:
------------------------------------------

    Assignee: Bertrand Delacretaz

> Restrict which classes can be deserialized
> ------------------------------------------
>
>                 Key: SLING-5288
>                 URL: https://issues.apache.org/jira/browse/SLING-5288
>             Project: Sling
>          Issue Type: Bug
>          Components: General
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>
> To avoid a recently reported Java deserialization vulnerability [1], we should restrict which classes are accepted when deserializing binaries.
> I have created a prototype SafeObjectInputStream at [2], which refuses to operate on classes that are outside a whitelist.
> We probably also need a wrapper for ObjectInputStreams provided by the environment, that looks a bit harder to create, for now we can already discuss this prototype to see if we want to pursue the idea.
> [1] https://blogs.apache.org/foundation/entry/apache_commons_statement_to_widespread
> [2] https://svn.apache.org/repos/asf/sling/whiteboard/bdelacretaz/safe-object-input-stream



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)