Deserialization of Untrusted Data vulnerability in Apache InLong.This issue affects Apache InLong: from 1.7.0 through 1.11.0,
the attackers can bypass using malicious parameters.
Users are advised to upgrade to Apache InLongs 1.12.0 or cherry-pick [1], [2] to solve it.
[1] https://github.com/apache/inlong/pull/9694
[2] https://github.com/apache/inlong/pull/9707
Weakness
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Inlong | Apache | 1.7.0 (including) | 1.12.0 (excluding) |
Potential Mitigations
- Make fields transient to protect them from deserialization.
- An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.
Related Attack Patterns
References
- http://www.openwall.com/lists/oss-security/2024/05/09/2
- https://github.com/advisories/GHSA-fgh3-pwmp-3qw3
- https://lists.apache.org/thread/d2hndtvh6bll4pkl91o2oqxyynhr54k3
- http://www.openwall.com/lists/oss-security/2024/05/09/2
- https://github.com/advisories/GHSA-fgh3-pwmp-3qw3
- https://lists.apache.org/thread/d2hndtvh6bll4pkl91o2oqxyynhr54k3