# CVE-2017-5985: Missing authorization in n/a

> Local users with lxc-usernet allocation can create host network interfaces and choose their names due to missing namespace ownership checks.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** Yes
- **Published:** 14 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-5985, GHSA-wxh2-mqg8-qff6, UBUNTU-CVE-2017-5985, USN-3224-1

## What is CVE-2017-5985?

CVE-2017-5985 is a low-severity missing authorization vulnerability in n/a, published on 14 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

lxc-user-nic in Linux Containers (LXC) allows local users with a lxc-usernet allocation to create network interfaces on the host and choose the name of those interfaces by leveraging lack of netns ownership check.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Linuxcontainers Lxc.

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

Apply the vendor's patch.

## Is CVE-2017-5985 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-8649](https://insights.sbomify.com/CVE-2016-8649/): Path traversal in LXC before 1.0.9 and 2.x before 2.0.6 (critical 9.1)
- [CVE-2016-10124](https://insights.sbomify.com/CVE-2016-10124/): Privilege escalation in n/a (high 8.6)
- [CVE-2017-18641](https://insights.sbomify.com/CVE-2017-18641/): Supply chain in n/a (high 8.1)
- [CVE-2013-6441](https://insights.sbomify.com/CVE-2013-6441/): Privilege escalation in n/a (high 7.2)
- [CVE-2015-1331](https://insights.sbomify.com/CVE-2015-1331/): Path traversal in n/a (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5985 is a low-severity missing authorization vulnerability in n/a, published on 14 Mar 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-5985 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-5985/ (Markdown: https://insights.sbomify.com/CVE-2017-5985/index.md)
```

## Sources

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

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