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

> Local attackers with matching UIDs can access sensitive cloud-init and snapd directories in images created by non-root users.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-759q-44f5-mjxr, UBUNTU-CVE-2017-10600

## What is CVE-2017-10600?

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

### Official description

ubuntu-image 1.0 before 2017-07-07, when invoked as non-root, creates files in the resulting image with the uid of the invoking user. When the resulting image is booted, a local attacker with the same uid as the image creator has unintended access to cloud-init and snapd directories.

Weakness: CWE-384 (Session Fixation)

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

It affects 1 product.


Products: Canonical Ubuntu-Image.

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

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

## Is CVE-2017-10600 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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