OS Command Injection in com.thoughtworks.xstream:xstream (CVE-2020-26217, CVSS 8.0)

Summary

OS command injection in com.thoughtworks.xstream:xstream (CVE-2020-26217). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.4.14-java7 or later.

Original description

The description as published by the source.

XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream's Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-26217 has been found in com.thoughtworks.xstream:xstream.
Successful exploitation can lead to full system takeover. CVSS score: 8.0/10.
What to do: upgrade com.thoughtworks.xstream:xstream to 1.4.14-java7 or later.
If unsure, ask your IT team or search "com.thoughtworks.xstream:xstream CVE-2020-26217" on the vendor's site.

CVE-2020-26217 (com.thoughtworks.xstream:xstream) — CWE-78 / CVSS v3 8.0
Attack vector: remote (network-reachable)
Patched: 1.4.14-java7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

OS command injection (CWE-78) exists in com.thoughtworks.xstream:xstream.

📍 Affected scope

Check the vendor advisory for the affected versions of com.thoughtworks.xstream:xstream.

🔥 Severity

Severity: High (CVSS 8.0/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.4.14-java7.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで com.thoughtworks.xstream:xstream を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade com.thoughtworks.xstream:xstream to 1.4.14-java7
```
ステージング環境で 1.4.14-java7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven com.thoughtworks.xstream:xstream

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.14-java7"}]}]

Bitnami activemq

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.15.14"}]},{"type":"SEMVER","events":[{"introduced":"5.16.0"},{"last_affected":"5.16.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2020-26217 libxstream-java Fixed in: 1.4.14-1

OS Command Injection in com.thoughtworks.xstream:xstream (CVE-2020-26217)