Pivotal Spring Framework before 6.0.0 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required.
Maintainers recommend investigating alternative components or a potential mitigating control. Version 4.2.6 and 3.2.17 contain enhanced documentation advising users to take precautions against unsafe Java deserialization, and version 6.0.0 and above deprecate the impacted classes.
References
- https://nvd.nist.gov/vuln/detail/CVE-2016-1000027
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-1000027
- https://security-tracker.debian.org/tracker/CVE-2016-1000027
- https://www.tenable.com/security/research/tra-2016-20
- https://github.com/spring-projects/spring-framework/issues/24434
- https://github.com/spring-projects/spring-framework/issues/24434#issuecomment-1231625331
- https://github.com/spring-projects/spring-framework/commit/5cbe90b2cd91b866a5a9586e460f311860e11cfa
- https://support.contrastsecurity.com/hc/en-us/articles/4402400830612-Spring-web-Java-Deserialization-CVE-2016-1000027
- https://github.com/spring-projects/spring-framework/issues/21680
- https://github.com/spring-projects/spring-framework/commit/2b051b8b321768a4cfef83077db65c6328ffd60f
- https://jira.spring.io/browse/SPR-17143?redirect=false
- https://github.com/advisories/GHSA-4wrc-f8pq-fpqp