← Back
CVE-2023-41334
Vulnerability in astropy (CVE-2023-41334)
Summary
vulnerability in astropy (CVE-2023-41334). Successful exploitation can lead to full system takeover. Exploitable via ``savelayout``. Mitigation: upgrade to `5.3.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2023-41334** has been found in astropy.
Attackers can target a specific entry point like ``savelayout`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade astropy to **5.3.3** or later.
If unsure, ask your IT team or search "astropy CVE-2023-41334" on the vendor's site.
CVE-2023-41334 (astropy) — CWE-74 /
Attack vector: local / unauthenticated / no user interaction
Attack surface: `savelayout` / `subprocess.Popen`
Patched: `5.3.3` — 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** (CWE-74) exists in astropy. Attackers reach the vulnerable code path via ``savelayout`` without authentication.
📍 Affected scope
astropy — . Attack surface: `savelayout` / `subprocess.Popen`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **5.3.3**.
🛡️ 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 'astropy' .` 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 'astropy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `astropy` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade astropy to 5.3.3ステージング環境で 5.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
astropy
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.3"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2023-41334
- advisory https://github.com/advisories/GHSA-h2x6-5jx5-46hf
- package https://github.com/astropy/astropy
- package https://pypi.org/project/astropy
- web https://github.com/astropy/astropy/security/advisories/GHSA-h2x6-5jx5-46hf
- web https://github.com/astropy/astropy/commit/22057d37b1313f5f5a9b5783df0a091d978dccb5
- web https://github.com/astropy/astropy/blob/9b97d98802ee4f5350a62b681c35d8687ee81d91/astropy/coordinates/transformations.py#L539