CVE-2022-39198
Published: 18 October 2022
Summary
CVE-2022-39198 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Apache Dubbo. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 6.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
A deserialization vulnerability in Apache Dubbo's hessian-lite component, present in version 3.2.12 and earlier, allows malicious code execution. The issue affects Apache Dubbo 2.7.x releases through 2.7.17, 3.0.x releases through 3.0.11, and 3.1.x releases through 3.1.0, and is tracked as CWE-502 with a CVSS 3.1 score of 9.8.
An unauthenticated attacker with network access can supply a crafted serialized payload that the server deserializes without sufficient validation, resulting in arbitrary code execution on the target system.
Advisories published on the Apache mailing lists describe the affected versions and direct users to upgrade to patched releases; the primary reference is available at https://lists.apache.org/thread/8d3zqrkoy4jh8dy37j4rd7g9jodzlvkk.
EPSS scores for the CVE rose from a low baseline to a peak of 0.2018, indicating increased exploitation interest after public disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-7031
Vulnerability details
A deserialization vulnerability existed in dubbo hessian-lite 3.2.12 and its earlier versions, which could lead to malicious code execution. This issue affects Apache Dubbo 2.7.x version 2.7.17 and prior versions; Apache Dubbo 3.0.x version 3.0.11 and prior versions; Apache Dubbo…
more
3.1.x version 3.1.0 and prior versions.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing supplies malicious serialized objects, detecting unsafe deserialization and supporting corrective actions.
Evaluation of untrusted data handling (deserialization testing) reveals unsafe processing, which the required remediation process addresses.
Untrusted serialized data can be deserialized and observed inside the chamber, blocking gadget-chain exploitation outside the sandbox.
Validates or rejects untrusted serialized data before deserialization occurs.
Identifies and blocks malicious code introduced through deserialization of untrusted data at system boundaries.
Integrity verification of serialized information can detect tampering before deserialization occurs.
Provenance of associated data allows detection of untrusted sources before deserialization or processing occurs.