| Gói / sản phẩm | Phiên bản bị ảnh hưởng | Phiên bản đã vá |
|---|---|---|
| org.springframework.integration:spring-integration-core | ≥ 4.3.0, < 4.3.23≥ 5.1.0, < 5.1.12≥ 5.2.0, < 5.2.8≥ 5.3.0, < 5.3.2 | 4.3.235.1.125.2.85.3.2 |
| banking corporate lending process management | = 14.2.0= 14.3.0= 14.5.0 | |
| banking credit facilities process management | = 14.2.0= 14.3.0= 14.5.0 | |
| banking supply chain finance | = 14.2.0= 14.3.0= 14.5.0 | |
| banking virtual account management | = 14.2.0= 14.3.0= 14.5.0 | |
| flexcube private banking | = 12.0.0= 12.1.0 | |
| retail customer management and segmentation foundation | ≥ 16.0, ≤ 19.0 | |
| retail merchandising system | = 16.0.3 | |
| spring integration | ≥ 4.3.0, ≤ 4.3.22≥ 5.1.0, ≤ 5.1.11≥ 5.2.0, ≤ 5.2.7≥ 5.3.0, ≤ 5.3.1 |
Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the "deserialization gadgets" exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown "deserialization gadgets" when configuring Kryo in code.
Bạn đang dùng một trong các sản phẩm này? Quét site để biết có đang lộ phiên bản có lỗ hổng không.
Quét site miễn phí