BitbucketApplication · Atlassian
CVE-2017-18087
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 · uneditedThe download commit resource in Atlassian Bitbucket Server from version 5.1.0 before version 5.1.7, from version 5.2.0 before version 5.2.5, from version 5.3.0 before version 5.3.3 and from version 5.4.0 before version 5.4.1 allows remote attackers to write files to disk potentially allowing them to gain code execution, exploit CVE-2017-1000117 if a vulnerable version of git is in use, and or determine if an internal service exists via an argument injection vulnerability in the at parameter.
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 confidenceArgument injection vulnerability in Bitbucket Server's download commit resource allows remote attackers to inject arbitrary arguments into git commands via the 'at' parameter. This enables file writing to disk, potential code execution, exploitation of CVE-2017-1000117 if vulnerable git is present, and internal service enumeration.
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
BitbucketApplication
>= 5.1.0, < 5.1.7>= 5.2.0, < 5.2.5>= 5.3.0, < 5.3.3> 5.4.0, < 5.4.1CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:L/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.
-
Locate Bitbucket Server versionAccess the Bitbucket Server admin interface and navigate to the 'About' page, or check the startup logs for the version number. The version is typically displayed in the footer of the admin UI or in the 'bitbucket.properties' config file in the Bitbucket home directory.Affected if The displayed version falls within any of these ranges: 5.1.0 to 5.1.6, 5.2.0 to 5.2.4, 5.3.0 to 5.3.2, or 5.4.0 to 5.4.0 (meaning versions 5.4.1 and later are not affected).
-
Confirm Bitbucket is runningVerify that the Bitbucket Server service is active and responding to HTTP requests. This can be done by accessing the Bitbucket web UI or checking that the Java process is running.Affected if Bitbucket Server is running any version in the affected ranges listed above.
-
Verify git version presentCheck the git executable version available to Bitbucket Server. This can be found in the Bitbucket admin UI under 'Git settings' or by running 'git --version' on the server where Bitbucket is installed.Affected if A vulnerable git version is present alongside an affected Bitbucket version, which could enable chained exploitation via CVE-2017-1000117.
If Bitbucket Server version is 5.1.7+, 5.2.5+, 5.3.3+, or 5.4.1+, the environment is not affected by this CVE. Otherwise, the argument injection vulnerability is present.
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 data5.1.75.2.55.3.3
Upgrade Bitbucket Server to version 5.1.7, 5.2.5, 5.3.3, 5.4.1 or later. Additionally, ensure git is patched to address CVE-2017-1000117.
Fix this in Bitbucket
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18087 — 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-2017-18087 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