CVE-2024-9070
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA deserialization vulnerability exists in BentoML's runner server in bentoml/bentoml versions <=1.3.4.post1. By setting specific parameters, an attacker can execute unauthorized arbitrary code on the server, causing severe harm. The vulnerability is triggered when the args-number parameter is greater than 1, leading to automatic deserialization and arbitrary code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA deserialization vulnerability exists in BentoML's runner server where setting the args-number parameter to a value greater than 1 triggers automatic deserialization of untrusted data, enabling arbitrary code execution on the affected server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify BentoML installationRun 'pip show bentoml' or 'pip list | grep -i bentoml' to check if BentoML is installedAffected if BentoML is not installed on the system
-
Check installed BentoML versionRun 'pip show bentoml' and note the Version field, then compare to the affected range (all versions up to and including 1.3.4.post1)Affected if The installed version is 1.3.4.post1 or earlier
-
Locate BentoML runner configurationSearch project directories for bentoml.yml, bentomodel.yaml, or Python files that initialize runners using Runner() or bentoml.run()Affected if No runner configuration files exist (not using runners)
-
Inspect args-number parameter usageGrep for 'args-number' or 'args_number' in configuration files and Python source code; also check any environment variables or deployment manifestsAffected if args-number is explicitly set to a value greater than 1, or defaults to a value greater than 1 in the runner configuration
The environment is affected if BentoML version 1.3.4.post1 or earlier is installed AND the runner server is used with args-number parameter set to any value greater than 1, enabling unsafe deserialization of input data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade BentoML to a version beyond 1.3.4.post1 once available, and as an interim control, implement input validation to restrict or sanitize the args-number parameter before deployment of the fix.
Latest stable BentoML release (version >1.3.4.post1)
- 1. Identify the current BentoML version installed by running: pip show bentoml or bentoml --version
- 2. If the installed version is <=1.3.4.post1, upgrade to the latest stable BentoML release using: pip install --upgrade bentoml
- 3. Verify the upgrade was successful by checking the new version with: pip show bentoml
- 4. Test that critical BentoML functionality works as expected after the upgrade
- 5. Review the BentoML release notes for the version you upgraded to for any additional security-related changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,528.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9070 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data