Skip to content

Hessian protocol configuration vulnerability in Apache Dubbo

Critical severity GitHub Reviewed Published Sep 8, 2021 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven org.apache.dubbo:dubbo (Maven)

Affected versions

>= 2.7.0, < 2.7.13
<= 2.6.10

Patched versions

2.7.13
2.6.10.1

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

References

Published by the National Vulnerability Database Sep 7, 2021
Reviewed Sep 8, 2021
Published to the GitHub Advisory Database Sep 8, 2021
Last updated Feb 1, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.287%
(68th percentile)

Weaknesses

CVE ID

CVE-2021-36163

GHSA ID

GHSA-cpx9-4rwv-486v

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.