Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2025-32375 β€” AI Deep Analysis Summary

CVSS 9.8 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: BentoML < 1.4.8 suffers from **Insecure Deserialization**. πŸ“‰ **Consequences**: Attackers can execute **Arbitrary Code** on the server. This breaks confidentiality, integrity, and availability completely.

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: **CWE-502** (Deserialization of Untrusted Data). The flaw lies in how BentoML processes unverified input, allowing malicious payloads to trigger code execution during the deserialization process.

Q3Who is affected? (Versions/Components)

πŸ‘₯ **Affected**: Users running **BentoML versions prior to 1.4.8**. Specifically, version **1.4.7** is confirmed vulnerable. πŸ“¦ Product: BentoML (Python AI model serving library).

Q4What can hackers do? (Privileges/Data)

πŸ’€ **Attacker Capabilities**: Full **Remote Code Execution (RCE)**. Hackers can run OS commands (e.g., `id`), steal data, and take over the system. ⚠️ Impact: **High** (C:H, I:H, A:H).

Q5Is exploitation threshold high? (Auth/Config)

πŸ”“ **Exploitation Threshold**: **LOW**. CVSS Vector: `AV:N/AC:L/PR:N/UI:N`. No authentication (PR:N), no user interaction (UI:N), and low complexity (AC:L). It is easily exploitable remotely.

Q6Is there a public Exp? (PoC/Wild Exploitation)

πŸ’£ **Public Exploit**: **YES**. A PoC is available on GitHub (theGEBIRGE/CVE-2025-32375). It uses Docker to spin up the vulnerable version and `exploit.py` to trigger RCE via `ncat` listener.…

Q7How to self-check? (Features/Scanning)

πŸ” **Self-Check**: 1. Check your BentoML version (`pip show bentoml`). 2. If version < 1.4.8, you are vulnerable. 3. Scan for untrusted deserialization inputs in your custom BentoML services.…

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Official Fix**: **YES**. The vulnerability was reported via GitHub Security Advisory (GHSA-7v4r-c989-xh26). The fix is included in **BentoML 1.4.8** and later. Update immediately! πŸ“… Published: 2025-04-09.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: If you cannot update, **strictly validate and sanitize all inputs** before deserialization. Disable any features that allow untrusted YAML/JSON deserialization.…

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Urgency**: **CRITICAL**. RCE with no auth required is a top-tier threat. πŸš€ **Priority**: Patch immediately. Update to BentoML >= 1.4.8. Monitor for active exploitation using the public PoC. Don't wait!