CVE-2025-10284
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 · uneditedBBOT's unarchive module could be abused by supplying malicious archives files and when extracted can then perform an arbitrary file write, resulting in remote 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 confidenceBBOT's unarchive module lacks proper path validation when extracting archive files, allowing attackers to craft malicious archives containing path traversal sequences (e.g., '../') that escape the intended extraction directory. This arbitrary file write capability enables attackers to overwrite system files, configurations, or place executable payloads, leading to remote code execution.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 BBOT installation and versionRun 'pip show bbot' or check your package manager for the installed bbot version. If installed from source, check the version in the source code or git tags.Affected if The installed version is any version of BBOT prior to the fix for CVE-2025-10284 and the unarchive module is in use
-
Locate the unarchive module configurationSearch for configuration files or CLI flags that reference 'unarchive' module in BBOT's config (usually in ~/.bbot/, bbot.yml, or command-line invocations).Affected if The unarchive module is explicitly enabled in BBOT's configuration or command execution
-
Check for active archive extraction workflowsReview BBOT scan logs or command history for invocations using the unarchive module, particularly with external or untrusted archive sources.Affected if BBOT has executed scans with the unarchive module enabled, especially against targets that may provide malicious archives
-
Verify module availabilityRun 'bbot -l' or 'bbot --list-modules' to confirm the unarchive module is present and available in your installation.Affected if The unarchive module is listed as available and the BBOT version is unpatched
You are affected if BBOT is installed with an unpatched version and the unarchive module has been or is enabled for processing archives from any source.
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.
From vendor dataImplement strict path validation using canonical path resolution (realpath or equivalent) to ensure extracted files remain within the intended target directory; reject any archive entries that resolve outside the extraction root. Additionally, consider sandboxing extraction and validating archive structure before extraction.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10284 — 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-2025-10284 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