← Back
CVE-2024-29032
Unsafe Deserialization in qiskit-ibm-runtime (CVE-2024-29032)
Summary
vulnerability in qiskit-ibm-runtime (CVE-2024-29032). Risk of unauthorized operations or information disclosure. Exploitable via ``qiskit_ibm_runtime.RuntimeDecoder``. Mitigation: upgrade to `0.21.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-29032** has been found in qiskit-ibm-runtime.
Attackers can target a specific entry point like ``qiskit_ibm_runtime.RuntimeDecoder`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade qiskit-ibm-runtime to **0.21.2** or later.
If unsure, ask your IT team or search "qiskit-ibm-runtime CVE-2024-29032" on the vendor's site.
CVE-2024-29032 (qiskit-ibm-runtime) — CWE-502 /
Attack vector: local / no user interaction
Attack surface: `qiskit_ibm_runtime.RuntimeDecoder` / `RuntimeDecoder` / `RuntimeEncoder` / `malicious_data`
Patched: `0.21.2` — 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
**unsafe deserialization** (CWE-502) exists in qiskit-ibm-runtime. Attackers reach the vulnerable code path via ``qiskit_ibm_runtime.RuntimeDecoder`` without authentication.
📍 Affected scope
qiskit-ibm-runtime — . Attack surface: `qiskit_ibm_runtime.RuntimeDecoder` / `RuntimeDecoder` / `RuntimeEncoder` / `malicious_data`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.21.2**.
🛡️ 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. Run `grep -r 'qiskit-ibm-runtime' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'qiskit-ibm-runtime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `qiskit-ibm-runtime` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade qiskit-ibm-runtime to 0.21.2ステージング環境で 0.21.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
qiskit-ibm-runtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0.1.0"},{"fixed":"0.21.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-29032
- advisory https://github.com/advisories/GHSA-x4x5-jv3x-9c7m
- package https://github.com/Qiskit/qiskit-ibm-runtime
- package https://pypi.org/project/qiskit-ibm-runtime
- web https://github.com/Qiskit/qiskit-ibm-runtime/security/advisories/GHSA-x4x5-jv3x-9c7m
- web https://github.com/Qiskit/qiskit-ibm-runtime/commit/b78fca114133051805d00043a404b25a33835f4d
- web https://github.com/Qiskit/qiskit-ibm-runtime/blob/16e90f475e78a9d2ae77daa139ef750cfa84ca82/qiskit_ibm_runtime/utils/json.py#L156-L159