Security readout for executives and security teams
Plain-English summary
Apache Dubbo deployments using the Hessian protocol can process HTTP POST bodies without applying configured type allow or block lists. That weakens a key safety control around deserialization. The issue is fixed in Dubbo 2.7.13 and 2.6.10.1.
Executive priority
Prioritize remediation where Dubbo Hessian services are internet-facing or exposed to untrusted networks. Internal-only deployments still deserve prompt upgrade because the flaw bypasses deserialization type controls.
Technical view
New HessianSkeleton instances were created without serialization factory configuration, so Dubbo properties for allowed and blocked type lists were not applied. The generic service is always exposed, reducing the attacker’s need to identify a valid service and method pair.
Likely exposure
Exposure is limited to Apache Dubbo 2.7.x and 2.6.x deployments that use the Hessian protocol, especially where Hessian HTTP provider endpoints are reachable by untrusted clients.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation. The source states attackers do not need a valid service and method pair because the generic service is exposed.
Researcher notes
Evidence is limited to the CVE description and Apache reference. No CVSS, CWE, exploit status, or detailed impact chain is provided in the bundle, so impact beyond unsafe deserialization should not be assumed.
Mitigation direction
- Upgrade Apache Dubbo 2.7.x to 2.7.13 or later.
- Upgrade Apache Dubbo 2.6.x to 2.6.10.1 or later.
- Identify and restrict externally reachable Hessian protocol endpoints.
- Check Apache Dubbo guidance before relying on configuration-only mitigations.
- Review allow and block list settings after upgrade.
Validation and detection
- Inventory Dubbo services and identify Hessian protocol usage.
- Confirm deployed Dubbo versions are 2.7.13, 2.6.10.1, or later.
- Verify Hessian provider endpoints are not publicly reachable unless required.
- Review configuration for intended allowed and blocked type lists.
- Check logs for unexpected Hessian POST traffic to provider endpoints.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-36163 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://lists.apache.org/thread.html/r8d0adc057bb15a37199502cc366f4b1164c9c536ce28e4defdb428c0%40%3Cdev.dubbo.apache.org%3ECVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.