changmingxie tcc-transaction Fastjson AutoType REST API Fastjson.parseObject deserialization
Description
A flaw has been found in changmingxie tcc-transaction up to 2.1.0. This issue affects the function Fastjson.parseObject of the component Fastjson AutoType REST API. This manipulation causes deserialization. It is possible to initiate the attack remotely. The vendor was contacted early about this disclosure but did not respond in any way.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Severe deserialization RCE in tcc-transaction up to 2.1.0 via Fastjson AutoType when attackers write crafted JSON payloads to Redis.
Vulnerability
A flaw in changmingxie tcc-transaction up to version 2.1.0 affects the component Fastjson AutoType REST API. The function Fastjson.parseObject is exposed via the REST API, and transaction data serialized with Fastjson is stored in Redis. When the system later deserializes this data during transaction recovery, the AutoType feature is enabled, allowing instantiation of arbitrary classes. This is a classic deserialization issue (CWE-502). All versions up to and including 2.1.0 are affected [1].
Exploitation
An attacker can initiate the attack remotely by writing a crafted JSON payload to Redis. The write path is accessible via the REST API, and in default deployments Redis may be unauthenticated, making the attack straightforward. The attacker supplies a JSON object containing a @type field that points to a malicious class. When Fastjson.parseObject() is called on the stored data, it instantiates the attacker-specified class, leading to arbitrary code execution [1]. No user interaction beyond the initial write is required; the trigger happens automatically during recovery.
Impact
Successful exploitation grants the attacker remote code execution (RCE) on the server hosting tcc-transaction. This can lead to full compromise of confidentiality, integrity, and availability. The attacker gains the privilege level of the application process, which may allow lateral movement within the infrastructure [1].
Mitigation
No official fix has been released by the vendor; they did not respond to disclosure. Mitigations include: disabling AutoType by setting ParserConfig.getGlobalInstance().setAutoTypeSupport(false) and enabling safeMode, using explicit type whitelists instead of AutoType, requiring authentication for Redis connections, and restricting Redis access to only application servers via network segmentation [1]. This CVE is not listed on CISA's Known Exploited Vulnerabilities (KEV) catalog at publication time.
AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2<=2.1.0+ 1 more
- (no CPE)range: <=2.1.0
- (no CPE)range: <=2.1.0
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
4- vuldb.com/submit/814092mitrethird-party-advisory
- github.com/Ku4D3/bug_story/blob/main/report_01.mdmitrerelated
- vuldb.com/vuln/365480mitrevdb-entrytechnical-description
- vuldb.com/vuln/365480/ctimitresignaturepermissions-required
News mentions
0No linked articles in our index yet.