BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-36109High confidence

Moby vulnerability relating to supplementary group permissions

moby · moby

Official source article: GitHub GHSA-RC4R-WH2Q-Q6C4 ↗. Check the applicable product and release in the original source.

5.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 32 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 23 Apr 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 1.04% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs moby moby and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 32 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communitydockerVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.20.10.18-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · communitydockerVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.20.10.18-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.21v3.21 · communitydockerVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.20.10.18-r0Alpine Security Database ↗Source updated 19 Aug 2026
Debian trixietrixie · sourcedocker.ioVendor fix publishedDebian records a fixed source-package version for this release.20.10.19+dfsg1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcedocker.ioVendor fix publishedDebian records a fixed source-package version for this release.20.10.19+dfsg1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcedocker.ioVendor fix publishedDebian records a fixed source-package version for this release.20.10.19+dfsg1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcedocker.ioVendor fix publishedDebian records a fixed source-package version for this release.20.10.19+dfsg1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Open-source package ranges1 source-attributed range

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
gogithub.com/docker/docker< 20.10.1820.10.18GitHub advisory ↗upstream repository advisory · 17 Jan 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-36109 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitymoby: supplementary groups mishandling
32 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • migration-toolkit-virtualization/mtv-controller-rhel9 as a component of Migration Toolkit for Virtualization
  • jenkins-operator-bundle-container as a component of OpenShift Developer Tools and Services
  • jenkins-operator-container as a component of OpenShift Developer Tools and Services
  • advanced-cluster-security/rhacs-scanner-rhel8 as a component of Red Hat Advanced Cluster Security 3
  • advanced-cluster-security/rhacs-scanner-slim-rhel8 as a component of Red Hat Advanced Cluster Security 3
  • assisted-installer-agent-container as a component of Red Hat OpenShift Container Platform 4
  • assisted-installer-container as a component of Red Hat OpenShift Container Platform 4
  • assisted-installer-reporter-container as a component of Red Hat OpenShift Container Platform 4
  • openshift-compliance-openscap-container as a component of Red Hat OpenShift Container Platform 4
  • openshift-compliance-operator-container as a component of Red Hat OpenShift Container Platform 4
  • openshift4-wincw/windows-machine-config-rhel8-operator as a component of Red Hat OpenShift Container Platform 4
  • openshift4/compliance-rhel8-operator as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in Moby. This flaw allows an attacker to bypass primary group restrictions due to a flaw in the supplementary group access setup.
Remediation
Fix deferred
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-6933

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 32 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The application performs an authorisation check, but it does not correctly enforce the required permission boundary.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

What

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.

Why

The application performs an authorisation check, but it does not correctly enforce the required permission boundary.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Incorrect Authorization → execute code or commands in the affected security context
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-863 ↗

CWE-863: Incorrect Authorization. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
Remote code executionCWE-863
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-0794Dell ECS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell ECS ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode mit Administratorrechten auszuführen, Informationen offenzulegen, Dateien zu manipulieren, einen Cross-Site-Scripting-Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2022-1738IBM InfoSphere Information Server: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM InfoSphere Information Server ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode auszuführen, einen Cross-Site-Scripting-Angriff durchzuführen, Informationen offenzulegen, einen Denial of Service Zustand herbeizuführen, Dateien zu manipulieren oder Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20220914Security Bulletin 14 Sep 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 14 Sep 2022, published on 14 September 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

CVERecord?id=CVE-2022-32206 Référence CVE CVE-2022-32207 https://www.cve.org/CVERecord?id=CVE-2022-32207 Référence CVE CVE-2022-32208 https://www.cve.org/CVERecord?id=CVE-2022-32208 Référence CVE CVE-2022-32221 https://www.cve.org/CVERecord?id=CVE-2022-32221 Référence CVE CVE-2022-3358 https://www.cve.org/CVERecord?id=CVE-2022-3358 Référence CVE CVE-2022-3509 https://www.cve.org/CVERecord?id=CVE-2022-3509 Référence CVE CVE-2022-3510 https://www.cve.org/CVERecord?id=CVE-2022-3510 Référence CVE CVE-2022-35252 https://www.cve.org/CVERecord?id=CVE-2022-35252 Référence CVE CVE-2022-3602 https://www.cve.org/CVERecord?id=CVE-2022-3602 Référence CVE CVE-2022-36109 https://www.cve.org/CVERecord?id=CVE-2022-36109 Référence CVE CVE-2022-3786 https://www.cve.org/CVERecord?id=CVE-2022-3786 Référence CVE CVE-2022-38749 https://www.cve.org/CVERecord?id=CVE-2022-38749 Référence CVE CVE-2022-38750 https://www.cve.org/CVERecord?id=CVE-2022-38750 Référence CVE CVE-2022-38751 https://www.cve.org/CVERecord?id=CVE-2022-38751 Référence CVE CVE-2022-38752 https://www.cve.org/CVERecord?id=CVE-2022-38752 Référence CVE CVE-2022-39399 https://www.cve.org/CVERecord?id=CVE-2022-39399 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-41715 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0622Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2022-32206 Référence CVE CVE-2022-32207 https://www.cve.org/CVERecord?id=CVE-2022-32207 Référence CVE CVE-2022-32208 https://www.cve.org/CVERecord?id=CVE-2022-32208 Référence CVE CVE-2022-32221 https://www.cve.org/CVERecord?id=CVE-2022-32221 Référence CVE CVE-2022-3358 https://www.cve.org/CVERecord?id=CVE-2022-3358 Référence CVE CVE-2022-35252 https://www.cve.org/CVERecord?id=CVE-2022-35252 Référence CVE CVE-2022-35929 https://www.cve.org/CVERecord?id=CVE-2022-35929 Référence CVE CVE-2022-3602 https://www.cve.org/CVERecord?id=CVE-2022-3602 Référence CVE CVE-2022-36056 https://www.cve.org/CVERecord?id=CVE-2022-36056 Référence CVE CVE-2022-36109 https://www.cve.org/CVERecord?id=CVE-2022-36109 Référence CVE CVE-2022-3786 https://www.cve.org/CVERecord?id=CVE-2022-3786 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-41715 https://www.cve.org/CVERecord?id=CVE-2022-41715 Référence CVE CVE-2022-41716 https://www.cve.org/CVERecord?id=CVE-2022-41716 Référence CVE CVE-2022-41717 https://www.cve.org/CVERecord?id=CVE-2022-41717 Référence CVE CVE-2022-41720 https://www.cve.org/CVERecord?id=CVE-2022-41720 Référence CVE CVE-2022-41722 https://www.cve.org/CVERecord?id=CVE-2022-41722 Référence CVE CVE-2022-41723 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-016867Moby Project の Moby 他複数ベンダの製品における脆弱性

Moby Project の Moby 他複数ベンダの製品には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 9 Sept 2022 · Last source change 23 Apr 2025, 17:12 UTC · CWE-863 · Incorrect Authorization

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-6933
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-6933↗Vendor CSAF · Red Hat Product Security↗Patch or update reference↗CVE authority or vendor reference · GitHub GHSA-RC4R-WH2Q-Q6C4↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-36109 · cve.blacktree.nl