Security readout for executives and security teams
Plain-English summary
This flaw affects images built with ubuntu-image 1.0 before July 7, 2017 when run as a non-root user. Some files in the generated image keep the builder's user ID, so a local user with the same UID on the booted system may gain unintended access to cloud-init and snapd directories.
Executive priority
Treat this as a targeted legacy exposure review, not an emergency remote compromise issue. Prioritize environments still running images from old non-root ubuntu-image build processes, especially where cloud-init data may contain operationally sensitive configuration.
Technical view
ubuntu-image incorrectly preserved the invoking non-root user's UID in the resulting image. On boot, ownership of cloud-init and snapd directories could map to a local account with the same UID, creating unintended local access. The provided sources do not include CVSS, CWE, package-version details beyond the date, or a detailed patch advisory.
Likely exposure
Exposure is most likely in older image-build pipelines that used ubuntu-image 1.0 before July 7, 2017 as a non-root user and deployed those images without rebuilding them.
Exploitation context
The CVE describes a local post-boot access issue requiring a local attacker with the same UID as the image creator. The source bundle does not show KEV listing, active exploitation, or remote exploitability.
Researcher notes
Evidence is narrow but clear: the issue is incorrect UID ownership in generated images. The supplied data lacks CVSS, CWE, exploit reports, detailed fixed version, and directory-specific paths, so validation should focus on build provenance and ownership inspection rather than assumed exploit chains.
Mitigation direction
- Check vendor guidance for the corrected ubuntu-image release.
- Rebuild affected images with a fixed ubuntu-image version.
- Replace deployed images created by vulnerable non-root builds.
- Restrict local access on systems booted from suspect images.
- Review cloud-init and snapd directory permissions on existing systems.
Validation and detection
- Inventory images built with ubuntu-image 1.0 before July 7, 2017.
- Identify builds where ubuntu-image was invoked by a non-root user.
- Inspect cloud-init and snapd directory ownership inside deployed images.
- Confirm ownership does not map to ordinary local users.
- Verify current image pipelines use a corrected ubuntu-image release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-10600 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://forum.snapcraft.io/t/ownership-bug-in-ubuntu-image/1285CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.