ObjectMessage#getObject currently would deserialize any value without performing input validation. Limiting supported classes via package prefixes seems to be a fairly standard solution [1][2][3].
CVE assigned to this issue: CVE-2016-6194.
- https://issues.apache.org/jira/browse/AMQ-6013
- https://jira.spring.io/browse/AMQP-590
- spring-projects/spring-amqp@4150f10