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