← Back
CVE-2022-46741
Out-of-Bounds Read in paddlepaddle (CVE-2022-46741)
Summary
vulnerability in paddlepaddle (CVE-2022-46741). Confidential information can be exposed externally. Exploitable via ``gather_tree``. Mitigation: upgrade to `2.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2022-46741** has been found in paddlepaddle.
Attackers can target a specific entry point like ``gather_tree`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade paddlepaddle to **2.4** or later.
If unsure, ask your IT team or search "paddlepaddle CVE-2022-46741" on the vendor's site.
CVE-2022-46741 (paddlepaddle) — CWE-125 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `gather_tree`
Patched: `2.4` — 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
**out-of-bounds read** (CWE-125) exists in paddlepaddle. Attackers reach the vulnerable code path via ``gather_tree`` without authentication.
📍 Affected scope
paddlepaddle — . Attack surface: `gather_tree`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.4**.
🛡️ 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 'paddlepaddle' .` 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 'paddlepaddle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `paddlepaddle` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade paddlepaddle to 2.4ステージング環境で 2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
paddlepaddle
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2022-46741
- advisory https://github.com/advisories/GHSA-2hvc-hwg3-hpvw
- package https://github.com/PaddlePaddle/Paddle
- package https://pypi.org/project/paddlepaddle
- web https://github.com/PaddlePaddle/Paddle/pull/47051
- web https://github.com/PaddlePaddle/Paddle/commit/6712e262fc6734873cc6d5ca4f45973339a88697
- web https://github.com/PaddlePaddle/Paddle/commit/ee6e6d511f9f33fc862c11722701fb5abb99ed94
- web https://github.com/PaddlePaddle/Paddle/blob/develop/security/advisory/pdsa-2022-001.md