Code Injection in sockeye (CVE-2021-43811)
Summary
Code injection in sockeye (CVE-2021-43811). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.3.24 or later.
Original description
The description as published by the source.
Impact
Sockeye uses YAML to store model and data configurations on disk. Versions below 2.3.24 use unsafe YAML loading, which can be made to execute arbitrary code embedded in config files.
An attacker can add malicious code to the config file of a trained model and attempt to convince users to download and run it. If users run the model, the embedded code will run locally.
Patches
The issue is fixed in version 2.3.24 and above by #964.
For more information
If you have any questions or comments about this advisory:
- Open an issue in awslabs/sockeye
- Email us at sockeye-dev
Attribution
This vulnerability was reported by Masatoshi Yoshizawa of yamory Security Team.
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-2021-43811 has been found in sockeye.
Successful exploitation can lead to full system takeover.
What to do: upgrade sockeye to 2.3.24 or later.
If unsure, ask your IT team or search "sockeye CVE-2021-43811" on the vendor's site.
CVE-2021-43811 (sockeye) — CWE-94
Attack vector: local / unauthenticated
Patched: 2.3.24 — 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.
Arbitrary code execution (CWE-94) exists in sockeye.
Check the vendor advisory for the affected versions of sockeye.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.3.24.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'sockeye' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'sockeye' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
sockeyeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade sockeye to 2.3.24ステージング環境で 2.3.24 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com