CVE-2025-10283
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 gitdumper module could be abused to execute commands through a malicious git repository.
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 confidenceThe gitdumper module in BBOT (an OSINT/reconnaissance tool) contains a command injection vulnerability that allows arbitrary command execution when processing a malicious git repository. The module likely unsafely handles git repository contents or hooks, enabling an attacker to execute OS commands on the target system.
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 'bbot --version' or check the installed package via pip with 'pip show bbot' to retrieve the version numberAffected if The installed version is older than the patched version released for CVE-2025-10283 or cannot be determined to be patched
-
Verify gitdumper module availabilityRun 'bbot -l' or 'bbot --help-modules' to list available modules and confirm gitdumper is presentAffected if The gitdumper module is listed as available in your BBOT installation
-
Check for recent gitdumper executionsReview command history, logs, or automation scripts that may have invoked bbot with the gitdumper module (e.g., bbot -m gitdumper)Affected if Gitdumper was run against any git repository, especially untrusted or externally-sourced repositories
-
Inspect gitdumper module configurationCheck BBOT configuration files (bbot.yml, .bbot.yml in home or project directory) for gitdumper settings or any custom hooksAffected if Gitdumper is enabled in configuration or custom git hooks are defined that could be manipulated
-
Review processed repository sourcesAudit any git repositories that were processed by the gitdumper module, checking for unexpected scripts in .git/hooks or unusual commit referencesAffected if Repositories processed were from untrusted sources or contain unexpected modifications to git hook files
You are affected if BBOT with the gitdumper module is installed and was used to process any git repository, particularly from untrusted sources, before applying the vendor-patched version.
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 dataAvoid using BBOT's gitdumper module on untrusted or unknown git repositories. Update to the patched version when released. Consider network isolation if processing external repositories is necessary.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10283 — 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-10283 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