CVE-2017-18037
Last modified
CVE-2017-18037 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.33% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Atlassian | Bitbucket | >= 3.7.0, < 4.14.11 |
| Atlassian | Bitbucket | >= 5.0.0, < 5.0.9 |
| Atlassian | Bitbucket | >= 5.1.0, < 5.1.8 |
| Atlassian | Bitbucket | >= 5.2.0, < 5.2.6 |
| Atlassian | Bitbucket | >= 5.3.0, < 5.3.4 |
| Atlassian | Bitbucket | >= 5.4.0, < 5.4.2 |
| Atlassian | Bitbucket | 5.5.0 |
| Atlassian | Bitbucket | 5.5.2 |
| Atlassian | Bitbucket | 5.5.3 |
| Atlassian | Bitbucket | 5.5.4 |
| Atlassian | Bitbucket | 5.5.5 |
| Atlassian | Bitbucket | 5.5.6 |
References
- https://jira.atlassian.com/browse/BSERV-10595Vendor Advisory
- https://jira.atlassian.com/browse/BSERV-10595Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-18037?
How severe is CVE-2017-18037?
How do I fix CVE-2017-18037?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-18030The cirrus_invalidate_region function in hw/display/cirrus_v…4.4
- CVE-2017-18032The download-manager plugin before 2.9.52 for WordPress has …
- CVE-2017-18033The Jira-importers-plugin in Atlassian Jira before version 7…
- CVE-2017-18034The source browse resource in Atlassian Fisheye and Crucible…
- CVE-2017-18035The /rest/review-coverage-chart/1.0/data/<repository_name>/.…
- CVE-2017-18036The Github repository importer in Atlassian Bitbucket Server…
- CVE-2017-18038The repository settings resource in Atlassian Bitbucket Serv…
- CVE-2017-18039The IncomingMailServers resource in Atlassian Jira from vers…
- CVE-2017-18040The viewDeploymentVersionCommits resource in Atlassian Bambo…
- CVE-2017-18041The viewDeploymentVersionJiraIssuesDialog resource in Atlass…
- CVE-2017-18042The update user administration resource in Atlassian Bamboo …
- CVE-2017-18043Integer overflow in the macro ROUND_UP (n, d) in Quick Emula…
Are you affected by CVE-2017-18037?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST