# CVE-2017-18912: Mattermost Server allows an attacker to specify a full pathname of a log file

> An attacker can specify a full pathname for a log file, potentially allowing unauthorized access to or modification of arbitrary files on the server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m2ch-x2q7-2284, GO-2026-4487

## What is CVE-2017-18912?

CVE-2017-18912 is a critical path traversal vulnerability in Mattermost Mattermost Server, published on 19 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Mattermost Server before 3.8.2, 3.7.5, and 3.6.7. It allows an attacker to specify a full pathname of a log file.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2017-18912?

3 open source packages ship an affected version, including github.com/mattermost/mattermost-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/mattermost/mattermost-server` | Go | All versions | None |
| `github.com/mattermost/mattermost-server` | Go | All versions | 3.7.4-0.20170404171331-0b5c0794fdcb |
| `github.com/mattermost/mattermost-server` | Go | All versions | 3.7.4-0.20170404171331-0b5c0794fdcb |

Products: Mattermost Mattermost Server.

## How do I fix CVE-2017-18912?

Upgrade github.com/mattermost/mattermost-server to 3.7.4-0.20170404171331-0b5c0794fdcb or later.

## Is CVE-2017-18912 being exploited?

There is no known exploitation of CVE-2017-18912 in the wild and no public exploit code.

## Other vulnerabilities in Mattermost Mattermost Server

- [CVE-2025-12419](https://insights.sbomify.com/CVE-2025-12419/): Account takeover on OAuth/OpenID-enabled servers (critical 9.9)
- [CVE-2025-12421](https://insights.sbomify.com/CVE-2025-12421/): Account Takeover via Code Exchange Endpoint (critical 9.9)
- [CVE-2025-4981](https://insights.sbomify.com/CVE-2025-4981/): Path Traversal Leading to RCE by Any Authenticated Mattermost User (critical 9.9)
- [CVE-2025-20051](https://insights.sbomify.com/CVE-2025-20051/): Arbitrary file read via block duplication in Mattermost Boards (critical 9.9)
- [CVE-2025-25279](https://insights.sbomify.com/CVE-2025-25279/): Arbitrary file read in Mattermost Boards via import & export board archive (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18912 and fix it if it is affected.

What it is: CVE-2017-18912 is a critical path traversal vulnerability in Mattermost Mattermost Server, published on 19 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18912 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/mattermost/mattermost-server (Go): affected all versions; no fix listed
- github.com/mattermost/mattermost-server (Go): affected all versions; fixed in 3.7.4-0.20170404171331-0b5c0794fdcb
- github.com/mattermost/mattermost-server (Go): affected all versions; fixed in 3.7.4-0.20170404171331-0b5c0794fdcb

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-18912/ (Markdown: https://insights.sbomify.com/CVE-2017-18912/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-18912
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-18912
- OSV: https://osv.dev/vulnerability/CVE-2017-18912

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-18912/
Summaries are generated and may contain mistakes; the official description above is the record.