dbcve.org
GitbucketApplication

CVE-2018-25332

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-17
Fix available
A fix is available. Upgrade to 4.24.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
GitBucket 4.23.1 contains an unauthenticated remote code execution vulnerability that allows attackers to execute arbitrary commands by exploiting weak secret token generation and insecure file upload functionality. Attackers can brute-force the Blowfish encryption key, upload a malicious JAR plugin via the git-lfs endpoint, and execute system commands through an exposed exploit endpoint.

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 · high confidence

Unauthenticated RCE vulnerability in GitBucket 4.23.1 allowing attackers to execute arbitrary system commands by brute-forcing a weak Blowfish encryption key and exploiting insecure file upload functionality to deploy malicious JAR plugins via the git-lfs endpoint.

MitigationUpgrade to the latest GitBucket version immediately and rotate any exposed encryption keys. If immediate patching is not feasible, disable the git-lfs endpoint and restrict network access to the application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitbucketApplication
Affected:< 4.24.0

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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify GitBucket version
    Check the GitBucket web interface footer for the version number, or inspect the gitbucket*.jar file in the WEB-INF/lib directory, or review startup logs
    Affected if Version is 4.23.1 or lower (any version below 4.24.0)
  2. Confirm git-lfs endpoint is enabled
    Attempt to access the /git-lfs/ path on the GitBucket server (e.g., GET request to http://your-server/git-lfs/)
    Affected if The endpoint returns a valid response rather than a 404 error, indicating git-lfs is active
  3. Verify network accessibility
    Determine if the GitBucket application is accessible from untrusted networks by checking firewall rules, reverse proxy configuration, or network ACLs
    Affected if The application is exposed to the internet or untrusted internal networks without authentication barriers
  4. Check for weak or default encryption keys
    Review GitBucket configuration files (init.properties or security.conf) for the Blowfish secret key setting; look for default or easily guessable values
    Affected if A default, weak, or unchanged Blowfish secret key is in use

You are affected if GitBucket is version 4.24.0 or earlier AND the git-lfs endpoint is enabled AND the application is network-accessible to unauthenticated attackers, especially if a weak encryption key is configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.24.0 or later
Fixed in 4.24.0
Vendor patch www.exploit-db.com →
Interim mitigation

Upgrade to the latest GitBucket version immediately and rotate any exposed encryption keys. If immediate patching is not feasible, disable the git-lfs endpoint and restrict network access to the application.

Recommended fix High confidence

GitBucket 4.24.0

  1. 1. Backup your GitBucket data directory and configuration files before proceeding
  2. 2. Stop the GitBucket service
  3. 3. Download and install GitBucket version 4.24.0 or later from the official GitBucket releases
  4. 4. Restore your data directory and configuration to the new installation
  5. 5. Start the GitBucket service
  6. 6. Verify the upgrade was successful by checking the GitBucket version in the admin panel
Caveat Review the GitBucket 4.24.0 release notes for any configuration or plugin compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gitbucket Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-25332 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-25332 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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