title: Unsafe deserialization in providers using the Hessian protocol
description: In Apache Dubbo, users may choose to use the Hessian protocol. The Hessian protocol is implemented on top of HTTP and passes the body of a POST request directly to a HessianSkeleton: New HessianSkeleton are created without any configuration of the serialization factory and therefore without applying the dubbo properties for applying allowed or blocked type lists. In addition, the generic service is always exposed and therefore attackers do not need to figure out a valid service/method name pair. This is fixed in 2.7.13, 2.6.10.1
problem types: Remote Code Execution by tempering the serialization id on server side.
affected:
{
product: Apache Dubbo
vendor: Apache Software Foundation
versions:
lessThanOrEqual: 2.7.12, status: affected, version: Apache Dubbo 2.7.x, versionType: custom
lessThanOrEqual: 2.6.10, status: affected, version: Apache Dubbo 2.6.x, versionType: custom
}