[SLING-5288] Restrict which classes can be deserialized

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: General
• Assignee: Bertrand Delacretaz
• Reporter: Bertrand Delacretaz
• Created: 10/Nov/15 13:37
• Updated: 25/Apr/16 14:12
• Resolved: 19/Nov/15 17:11

Description

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

Issue Links

• relates to: IO-487 ValidatingObjectInputStream contribution - restrict which classes can be deserialized
• relates to: SLING-5685 Upgrade Commons IO to 2.5