← Back
CVE-2024-41951
Vulnerability in pheonixappapi (CVE-2024-41951)
Summary
vulnerability in pheonixappapi (CVE-2024-41951). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.2.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-41951** has been found in pheonixappapi.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade pheonixappapi to **0.2.5** or later.
If unsure, ask your IT team or search "pheonixappapi CVE-2024-41951" on the vendor's site.
CVE-2024-41951 (pheonixappapi) — CWE-323 /
Attack vector: local / no user interaction
Patched: `0.2.5` — apply immediately
Workaround: There is a fix to this problem but it requires modifying the code.
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-323) exists in pheonixappapi.
📍 Affected scope
pheonixappapi — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.2.5**.
🛡️ Workaround
Workaround: There is a fix to this problem but it requires modifying the code.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'pheonixappapi' .` 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 'pheonixappapi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pheonixappapi` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There is a fix to this problem but it requires modifying the code.パッチが適用されるまでの応急処置として、There is a fix to this problem but it requires modifying the code. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade pheonixappapi to 0.2.5ステージング環境で 0.2.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
pheonixappapi
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.2.5"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-41951
- advisory https://github.com/advisories/GHSA-258h-f687-4226
- package https://github.com/AkshuDev/PheonixAppAPI
- package https://pypi.org/project/pheonixappapi
- web https://github.com/AkshuDev/PheonixAppAPI/security/advisories/GHSA-258h-f687-4226
- web https://github.com/AkshuDev/PheonixAppAPI/commit/0937419e323f5ea9013d43dc1b82fef9d7e05044