Vulnerability in XMSS/XMSS^MT private key deserialization (CVE-2018-1000613)

Summary

Vulnerability in XMSS/XMSS^MT private key deserialization (CVE-2018-1000613). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.60 or later.

Original description

The description as published by the source.

Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60 contains a CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in XMSS/XMSS^MT private key deserialization that can result in Deserializing an XMSS/XMSS^MT private key can result in the execution of unexpected code. This attack appear to be exploitable via A handcrafted private key can include references to unexpected classes which will be picked up from the class path for the executing application. This vulnerability appears to have been fixed in 1.60 and later.

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-2018-1000613 has been found in XMSS/XMSS^MT private key deserialization.
Successful exploitation can lead to full system takeover.
What to do: upgrade XMSS/XMSS^MT private key deserialization to 1.60 or later.
If unsure, ask your IT team or search "XMSS/XMSS^MT private key deserialization CVE-2018-1000613" on the vendor's site.

CVE-2018-1000613 (XMSS/XMSS^MT private key deserialization)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.60 — 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

A vulnerability (unclassified) exists in XMSS/XMSS^MT private key deserialization.

📍 Affected scope

Check the vendor advisory for the affected versions of XMSS/XMSS^MT private key deserialization.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.60.

🛡️ 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・依存マニフェストで XMSS/XMSS^MT private key deserialization を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade XMSS/XMSS^MT private key deserialization to 1.60
```
ステージング環境で 1.60 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2018-1000613 bouncycastle Fixed in: 1.60-1

References

advisory lists.opensuse.org
advisory security.netapp.com
patch github.com
patch github.com
patch oracle.com
patch oracle.com
patch oracle.com
patch oracle.com
patch oracle.com
patch oracle.com
web lists.apache.org