Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2022-36109: Moby vulnerability relating to supplementary group permissions

Noroxi assessment

Priority: Monitor (action score 25/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 64.5% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: docker (Alpine:v3.16) 20.10.18-r0; docker.io (Debian:12) 20.10.19+dfsg1-1; github.com/containerd/containerd (Go) 1.6.18, 1.5.18.

Low priority for now. Upgrade to docker (Alpine:v3.16) 20.10.18-r0; docker.io (Debian:12) 20.10.19+dfsg1-1; github.com/containerd/containerd (Go) 1.6.18, 1.5.18 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Moby is an open-source project created by Docker to enable software containerization. A bug was found in Moby (Docker Engine) where supplementary groups are not set up properly. If an attacker has direct access to a container and manipulates their supplementary group access, they may be able to use supplementary group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive information or gaining the ability to execute code in that container. This bug is fixed in Moby (Docker Engine) 20.10.18. Running containers should be stopped and restarted for the permissions to be fixed. For users unable to upgrade, this problem can be worked around by not using the `"USER $USERNAME"` Dockerfile instruction. Instead by calling `ENTRYPOINT ["su", "-", "user"]` the supplementary groups will be set up properly.

MediumCVSS 6.3 · v3.1—No exploit Fix available
Published
Sep 9, 2022
Updated
Jun 17, 2026
EPSS
1.0% · 64th percentile

Report tools

JSON

Action score

25

Monitor

Low priority for now.

CVSS
25 / 40 · 6.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.0%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.3
CNA · GitHub_M
5.3
1.0 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-36109

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for mobyproject records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
mobyprojectmoby
fedoraprojectfedora

Using moby? Add it to your stack and be the first to know about CVEs like this one. (Docker)

Watch new CVEs for moby

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every Monday

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora36
  • fedoraproject fedora37
  • mobyproject mobybefore 20.10.18

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • moby moby

    • < 20.10.18affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.16dockerbefore 20.10.18-r020.10.18-r0
Debian:12docker.iobefore 20.10.19+dfsg1-120.10.19+dfsg1-1
Gogithub.com/containerd/containerdfrom 1.6.0 · before 1.6.181.6.18
Gogithub.com/containerd/containerdbefore 1.5.181.5.18
Gogithub.com/containers/buildahbefore 1.27.11.27.1
Gogithub.com/docker/dockerbefore 20.10.1820.10.18
Gogithub.com/docker/dockerbefore 20.10.18+incompatible20.10.18+incompatible
openSUSE:Leap Micro 5.3dockerbefore 20.10.23_ce-150000.175.120.10.23_ce-150000.175.1
openSUSE:Tumbleweeddockerbefore 20.10.23_ce-2.120.10.23_ce-2.1
SUSE:Linux Enterprise Micro 5.3dockerbefore 20.10.23_ce-150000.175.120.10.23_ce-150000.175.1
SUSE:Linux Enterprise Module for Containers 12dockerbefore 20.10.23_ce-98.89.120.10.23_ce-98.89.1

Same product

mobyproject: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-28840moby/moby's dockerd daemon encrypted overlay network may be unauthenticated
    35Monitor
  • CVE-2024-36623moby through v25.0.3 has a Race Condition vulnerability in the streamformatter package which can be used to trigger multiple concurrent writ
    32Monitor
  • CVE-2024-24557Moby classic builder cache poisoning
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2021-41091Oct 4, 2021 · Insufficiently restricted permissions on data directory in Docker Engine
    26Monitor
  • ← EarlierCVE-2022-24769Mar 24, 2022 · Default inheritable capabilities for linux container should be empty
    23Monitor
  • Later →CVE-2023-28841Apr 4, 2023 · moby/moby's dockerd daemon encrypted overlay network traffic may be unencrypted
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:docker20.10.18-r0 · Alpine:v3.16Package registry (OSV)
debian:docker.io20.10.19+dfsg1-1 · Debian:12Package registry (OSV)
Go:github.com/containerd/containerd1.5.18Package registry (OSV)
Go:github.com/containerd/containerd1.6.18Package registry (OSV)
Go:github.com/containers/buildah1.27.1Package registry (OSV)
Go:github.com/docker/docker20.10.18Package registry (OSV)
Go:github.com/docker/docker20.10.18+incompatiblePackage registry (OSV)
opensuse:docker20.10.23_ce-150000.175.1 · openSUSE:Leap Micro 5.3Package registry (OSV)
suse:docker20.10.23_ce-150000.175.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
Low

Weakness class (CWE)

CWE-863 · Incorrect Authorization

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records