Pivotal Spring Framework through 5.3.16 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. NOTE: the vendor's position is that untrusted data is not an intended use case. The product's behavior will not be changed because some users rely on deserialization of trusted data.
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Link | Tags |
---|---|
https://www.tenable.com/security/research/tra-2016-20 | third party advisory exploit |
https://raw.githubusercontent.com/distributedweaknessfiling/cvelist/master/2016/1000xxx/CVE-2016-1000027.json | exploit third party advisory broken link |
https://security-tracker.debian.org/tracker/CVE-2016-1000027 | third party advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-1000027 | issue tracking third party advisory |
https://github.com/spring-projects/spring-framework/issues/24434#issuecomment-579669626 | issue tracking third party advisory |
https://github.com/spring-projects/spring-framework/issues/24434#issuecomment-582313417 | issue tracking third party advisory |
https://spring.io/blog/2022/05/11/spring-framework-5-3-20-and-5-2-22-available-now | third party advisory release notes |
https://github.com/spring-projects/spring-framework/issues/24434#issuecomment-744519525 | issue tracking third party advisory |
https://security.netapp.com/advisory/ntap-20230420-0009/ |