Untrusted data deserialization vulnerability exists in a-blog cms. Processing a specially crafted request may store arbitrary files on the server where the product is running. This can be leveraged to execute an arbitrary script on the server.
Weakness
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| A-blog_cms | Appleple | * | 2.8.80 (including) |
| A-blog_cms | Appleple | 2.9.0 (including) | 2.9.46 (including) |
| A-blog_cms | Appleple | 2.10.0 (including) | 2.10.58 (excluding) |
| A-blog_cms | Appleple | 2.11.0 (including) | 2.11.70 (excluding) |
| A-blog_cms | Appleple | 3.0.0 (including) | 3.0.41 (excluding) |
| A-blog_cms | Appleple | 3.1.0 (including) | 3.1.37 (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.