Unauthorized file access via omitted supplementary GID
Published Sep 9, 2022 · Updated Apr 23, 2025
Incorrect group initialization in Moby before 20.10.18 allows local users in a container to bypass primary-group file restrictions. The daemon's getUser function omits the effective GID from AdditionalGids, so a set-group executable can drop the primary group. Code execution inside a Linux container, a set-group executable, and negative group permissions are required; the bypass permits otherwise denied file access within that container.
Summary
What happened
Incorrect group initialization in Moby before 20.10.18 allows local users in a container to bypass primary-group file restrictions. The daemon's getUser function omits the effective GID from AdditionalGids, so a set-group executable can drop the primary group. Code execution inside a Linux container, a set-group executable, and negative group permissions are required; the bypass permits otherwise denied file access within that container.
The record
- CVE
- CVE-2022-36109
- Published
- Sep 9, 2022
- Updated
- Apr 23, 2025
- Vendor
- Moby Project
- Product
- Moby
- Classifications
- T1548.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 9, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 20.10.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- permission-experiment proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo