# CVE-2017-8108: Path traversal in n/a

> Local attackers can exploit symlink vulnerabilities in temporary files to write arbitrary data or escalate privileges in Lynis.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-8108, GHSA-rm6c-xgjf-vhwg, UBUNTU-CVE-2017-8108

## What is CVE-2017-8108?

CVE-2017-8108 is a high-severity path traversal vulnerability in n/a, published on 8 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified tests in Lynis before 2.5.0 allow local users to write to arbitrary files or possibly gain privileges via a symlink attack on a temporary file.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Cisofy Lynis.

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

Upgrade to a fixed version.

## Is CVE-2017-8108 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-13882](https://insights.sbomify.com/CVE-2020-13882/): Race condition in n/a (medium 4.2)
- [CVE-2019-13033](https://insights.sbomify.com/CVE-2019-13033/): Information disclosure in n/a (low 3.3)
- [CVE-2014-3982](https://insights.sbomify.com/CVE-2014-3982/): Path traversal in n/a (low 3.3)
- [CVE-2014-3986](https://insights.sbomify.com/CVE-2014-3986/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8108 is a high-severity path traversal vulnerability in n/a, published on 8 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8108 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-8108/ (Markdown: https://insights.sbomify.com/CVE-2017-8108/index.md)
```

## Sources

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

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