# CVE-2017-1086: Information disclosure in FreeBSD

> A local attacker with debugger access can read uninitialized kernel stack memory via ptrace, potentially exposing sensitive kernel data.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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-hh28-cq4w-7g55

## What is CVE-2017-1086?

CVE-2017-1086 is a low-severity 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 before 11.1-STABLE, 11.1-RELEASE-p4, 11.0-RELEASE-p15, 10.4-STABLE, 10.4-RELEASE-p3, and 10.3-RELEASE-p24, not all information in the struct ptrace_lwpinfo is relevant for the state of any thread, and the kernel does not fill the irrelevant bytes or short strings. Since the structure filled by the kernel is allocated on the kernel stack and copied to userspace, a leak of information of the kernel stack of the thread is possible from the debugger. As a result, some bytes from the kernel stack of the thread using ptrace (PT_LWPINFO) call can be observed in userspace.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Freebsd Freebsd.

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

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

## Is CVE-2017-1086 being exploited?

There is no known exploitation of CVE-2017-1086 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-1086 and fix it if it is affected.

What it is: CVE-2017-1086 is a low-severity 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-1086 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-1086/ (Markdown: https://insights.sbomify.com/CVE-2017-1086/index.md)
```

## Sources

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

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