# CVE-2017-1087: Path traversal in FreeBSD

> A jail isolation flaw allows attackers to modify shared memory, potentially causing denial of service or local privilege escalation.

- **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:** No
- **Published:** 16 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cfm3-j9mw-w24h

## What is CVE-2017-1087?

CVE-2017-1087 is a high-severity path traversal vulnerability in Freebsd Freebsd, published on 16 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In FreeBSD 10.x before 10.4-STABLE, 10.4-RELEASE-p3, and 10.3-RELEASE-p24 named paths are globally scoped, meaning a process located in one jail can read and modify the content of POSIX shared memory objects created by a process in another jail or the host system. As a result, a malicious user that has access to a jailed system is able to abuse shared memory by injecting malicious content in the shared memory region. This memory region might be executed by applications trusting the shared memory, like Squid. This issue could lead to a Denial of Service or local privilege escalation.

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

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

It affects 1 product.


Products: Freebsd Freebsd.

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

No fix has been published for CVE-2017-1087 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-1087 being exploited?

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

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1087 is a high-severity path traversal vulnerability in Freebsd Freebsd, published on 16 Nov 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-1087 in the wild and no public exploit code.

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

## Sources

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

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