Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2017-18037

6.5 · MEDIUM
Published Feb 2, 2018 atlassian CWE-22 EPSS 1.30% (68th pctl)

Overview

CVE-2017-18037 is a medium-severity vulnerability affecting atlassian bitbucket. It was published on February 2, 2018 and has a CVSS 3.0 base score of 6.5 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 6.5, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical Description

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.

Remediation

Check the references section for vendor advisories and patches from atlassian. Update bitbucket to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
atlassian bitbucket >= 3.7.0, < 4.14.11 Affected

Frequently Asked Questions

What is CVE-2017-18037?

CVE-2017-18037 is a medium-severity vulnerability affecting atlassian bitbucket. It was published on February 2, 2018 and has a CVSS 3.0 base score of 6.5 (MEDIUM).

How severe is CVE-2017-18037?

This vulnerability has a CVSS 3.0 base score of 6.5, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2017-18037?

Check the references section for vendor advisories and patches from atlassian. Update bitbucket to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-18037?

CyberStrike's AI-powered security agents can automatically detect CVE-2017-18037 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.