Skip to content
Noroxi
CVE-2017-18037· NVD / CVE Program· CNA atlassian

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 ve

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.

MediumCVSS 6.5 · v3.0—No exploit No fix recorded
Published
Feb 2, 2018
Updated
Jun 16, 2026
EPSS
1.3% · 69th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

Affected systems

VendorProduct
atlassianbitbucket

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • atlassian bitbucket3.7.0 and later · before 4.14.11
  • atlassian bitbucket5.0.0 and later · before 5.0.9
  • atlassian bitbucket5.1.0 and later · before 5.1.8
  • atlassian bitbucket5.2.0 and later · before 5.2.6
  • atlassian bitbucket5.3.0 and later · before 5.3.4
  • atlassian bitbucket5.4.0 and later · before 5.4.2
  • atlassian bitbucket5.5.0
  • atlassian bitbucket5.5.2
  • atlassian bitbucket5.5.3
  • atlassian bitbucket5.5.4
  • atlassian bitbucket5.5.5
  • atlassian bitbucket5.5.6

Versions reported by the vendor

Affected version ranges reported by the assigning authority (atlassian). Independent of NVD's CPE analysis and usually ahead of it.

  • Atlassian Bitbucket Server

    • from 3.7.0 prior to 4.14.11, from 5.0.0 prior to 5.0.9, from 5.1.0 prior to 5.1.8, from 5.2.0 prior to 5.2.6, from 5.3.0 prior to 5.3.4, from 5.4.0 prior to 5.4.2, from 5.5.0 prior to 5.5.1affected

Other highest-scoring records for the same primary product.

  • CVE-2022-36804Multiple API endpoints in Atlassian Bitbucket Server and Data Center 7.0.0 before version 7.6.17, from version 7.7.0 before version 7.17.10,KEV
    95Now
  • CVE-2022-43781There is a command injection vulnerability using environment variables in Bitbucket Server and Data Center.
    68This week
  • CVE-2019-15000The commit diff rest endpoint in Bitbucket Server and Data Center before 5.16.10 (the fixed version for 5.16.x ), from 6.0.0 before 6.0.10 (
    41Plan
  • CVE-2018-5225In browser editing in Atlassian Bitbucket Server from version 4.13.0 before 5.4.8 (the fixed version for 4.13.0 through 5.4.7), 5.5.0 before
    40Plan
  • CVE-2019-3397Atlassian Bitbucket Data Center licensed instances starting with version 5.13.0 before 5.13.6 (the fixed version for 5.13.x), from 5.14.0 be
    37Monitor
  • CVE-2019-20097Bitbucket Server and Bitbucket Data Center versions starting from 1.0.0 before 5.16.11, from version 6.0.0 before 6.0.11, from version 6.1.0
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records