dbcve.org
BitbucketApplication · Atlassian

CVE-2017-18037

MEDIUM · 6.5 CVSS v3.0 Published 2018-02-02
Fix available
A fix is available. Upgrade to 4.14.11 / 5.0.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The git repository tag rest resource in Atlassian Bitbucket Server from version 3.7.0 before 4.14.11 (the fixed version for 4.14.x), from version 5.0.0 before 5.0.9 (the fixed version for 5.0.x), from version 5.1.0 before 5.1.8 (the fixed version for 5.1.x), from version 5.2.0 before 5.2.6 (the fixed version for 5.2.x), from version 5.3.0 before 5.3.4 (the fixed version for 5.3.x), from version 5.4.0 before 5.4.2 (the fixed version for 5.4.x), from version 5.5.0 before 5.5.1 (the fixed version for 5.5.x) and before 5.6.0 allows remote attackers to read arbitrary files via a path traversal vulnerability through the name of a git tag.

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

This is a path traversal vulnerability in Atlassian Bitbucket Server's git repository tag REST API. Attackers can manipulate the git tag name parameter to include path traversal sequences (e.g., ../../), allowing unauthorized read access to arbitrary files on the server filesystem outside the intended repository directory.

MitigationUpgrade Bitbucket Server to the fixed versions (4.14.11+, 5.0.9+, 5.1.8+, 5.2.6+, 5.3.4+, 5.4.2+, 5.5.1+, or 5.6.0+) to remediate this vulnerability.

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
Affected:>= 3.7.0, < 4.14.11>= 5.0.0, < 5.0.9>= 5.1.0, < 5.1.8>= 5.2.0, < 5.2.6>= 5.3.0, < 5.3.4>= 5.4.0, < 5.4.2= 5.5.0= 5.5.2= 5.5.3= 5.5.4= 5.5.5= 5.5.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 the Bitbucket Server version
    Check the Bitbucket interface by navigating to the administration settings, or examine the bitbucket-version.txt file in the Bitbucket home directory, or run: cd /opt/bitbucket && ./bin/version.sh or check the installation logs
    Affected if The installed version falls within any of these vulnerable ranges: 3.7.0 to 4.14.10, 5.0.0 to 5.0.8, 5.1.0 to 5.1.7, 5.2.0 to 5.2.5, 5.3.0 to 5.3.3, 5.4.0 to 5.4.1, or exactly 5.5.0, 5.5.2, 5.5.3, 5.5.4, 5.5.5, or 5.5.6
  2. Confirm Bitbucket REST API is accessible
    Verify the Bitbucket Server web interface and REST API endpoints are reachable over the network. The vulnerable endpoint is /rest/git/1.0/projects/{project}/repos/{repo}/tags
    Affected if The REST API is externally accessible without proper authentication controls or the server is directly exposed to untrusted networks
  3. Verify git repository tags functionality is in use
    Check if any git repositories exist in Bitbucket that utilize the tagging feature, as the vulnerability specifically affects the tag REST API endpoint
    Affected if Repositories with git tag functionality are present and the tag REST API endpoint is available

A user is affected if their Bitbucket Server version matches one of the vulnerable version ranges AND the REST API endpoint for git tags is accessible.

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.

From vendor data
Upgrade available Upgrade to 4.14.11 / 5.0.9 / 5.1.8 or later
Fixed in 4.14.115.0.95.1.8
Interim mitigation

Upgrade Bitbucket Server to the fixed versions (4.14.11+, 5.0.9+, 5.1.8+, 5.2.6+, 5.3.4+, 5.4.2+, 5.5.1+, or 5.6.0+) to remediate this vulnerability.

Fix this in Bitbucket Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-18037 — 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-2017-18037 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