BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-29162High confidence

Incorrect Default Permissions in runc

opencontainers · runc

5.9MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
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
SSA-806742 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-806742: Multiple Vulnerabilities in SCALANCE XCM-/XRM-300 before V2.4
11 known affected

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

  • SCALANCE XCH328 (6GK5328-4TS01-2EC2)
  • SCALANCE XCM324 (6GK5324-8TS01-2AC2)
  • SCALANCE XCM328 (6GK5328-4TS01-2AC2)
  • SCALANCE XCM332 (6GK5332-0GA01-2AC2)
  • SCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)
  • SCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)
  • SCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)
  • SCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)
  • SCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)
  • SCALANCE XRM334 (2x230 V AC, 12xFO) (6GK5334-3TS01-4AR3)
  • SCALANCE XRM334 (2x230 V AC, 8xFO) (6GK5334-2TS01-4AR3)
Summary
runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix changes `runc exec --cap` behavior such that the additional capabilities granted to the process being executed (as specified via `--cap` arguments) do not include inheritable capabilities. In addition, `runc spec` is changed to not set any inheritable capabilities in the created example OCI spec (`config.json`) file.
Remediation
Update to V2.4 or later version
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-3675

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix changes `runc exec --cap` behavior such that the additional capabilities granted to the process being executed (as specified via `--cap` arguments) do not include inheritable capabilities. In addition, `runc spec` is changed to not set any inheritable capabilities in the created example OCI spec (`config.json`) file.

What

runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix changes `runc exec --cap` behavior such that the additional capabilities granted to the process being executed (as specified via `--cap` arguments) do not include inheritable capabilities. In addition, `runc spec` is changed to not set any inheritable capabilities in the created example OCI spec (`config.json`) file.

Why

During installation, installed file permissions are set to allow anyone to modify those files.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may gain additional privileges.

What

runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in runc 1.1.2. This fix changes `runc exec --cap` behavior such that the additional capabilities granted to the process being executed (as specified via `--cap` arguments) do not include inheritable capabilities. In addition, `runc spec` is changed to not set any inheritable capabilities in the created example OCI spec (`config.json`) file.

Why

During installation, installed file permissions are set to allow anyone to modify those files.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may gain additional privileges.

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 Default Permissions → gain additional privileges
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
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-276 ↗

CWE-276: Incorrect Default Permissions. During installation, installed file permissions are set to allow anyone to modify those files.

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:N/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.PRNonePrivileges required: The attacker does not need an account or existing 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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedPrivilege escalationCWE-276
A

Official authority intelligence

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

BSI · German · WID-SEC-W-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-W-2022-2052Mehrere Red Hat Enterprise Linux Pakete: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen oder sonstige Auswirkungen zu verursachen.

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0590Multiples vulnérabilités dans les produits IBM

d?id=CVE-2021-35516 Référence CVE CVE-2021-35517 https://www.cve.org/CVERecord?id=CVE-2021-35517 Référence CVE CVE-2021-36090 https://www.cve.org/CVERecord?id=CVE-2021-36090 Référence CVE CVE-2021-41103 https://www.cve.org/CVERecord?id=CVE-2021-41103 Référence CVE CVE-2021-43784 https://www.cve.org/CVERecord?id=CVE-2021-43784 Référence CVE CVE-2021-43816 https://www.cve.org/CVERecord?id=CVE-2021-43816 Référence CVE CVE-2022-23471 https://www.cve.org/CVERecord?id=CVE-2022-23471 Référence CVE CVE-2022-23648 https://www.cve.org/CVERecord?id=CVE-2022-23648 Référence CVE CVE-2022-27664 https://www.cve.org/CVERecord?id=CVE-2022-27664 Référence CVE CVE-2022-29162 https://www.cve.org/CVERecord?id=CVE-2022-29162 Référence CVE CVE-2022-31030 https://www.cve.org/CVERecord?id=CVE-2022-31030 Référence CVE CVE-2022-32149 https://www.cve.org/CVERecord?id=CVE-2022-32149 Référence CVE CVE-2022-41721 https://www.cve.org/CVERecord?id=CVE-2022-41721 Référence CVE CVE-2022-41723 https://www.cve.org/CVERecord?id=CVE-2022-41723 Référence CVE CVE-2023-21830 https://www.cve.org/CVERecord?id=CVE-2023-21830 Référence CVE CVE-2023-25153 https://www.cve.org/CVERecord?id=CVE-2023-25153 Référence CVE CVE-2023-25173 https://www.cve.org/CVERecord?id=CVE-2023-25173 Référence CVE CVE-2023-25809 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0366Multiples vulnérabilités dans les produits IBM

d?id=CVE-2020-28493 Référence CVE CVE-2021-28363 https://www.cve.org/CVERecord?id=CVE-2021-28363 Référence CVE CVE-2021-30465 https://www.cve.org/CVERecord?id=CVE-2021-30465 Référence CVE CVE-2021-43565 https://www.cve.org/CVERecord?id=CVE-2021-43565 Référence CVE CVE-2021-43784 https://www.cve.org/CVERecord?id=CVE-2021-43784 Référence CVE CVE-2021-45958 https://www.cve.org/CVERecord?id=CVE-2021-45958 Référence CVE CVE-2022-23539 https://www.cve.org/CVERecord?id=CVE-2022-23539 Référence CVE CVE-2022-23540 https://www.cve.org/CVERecord?id=CVE-2022-23540 Référence CVE CVE-2022-23541 https://www.cve.org/CVERecord?id=CVE-2022-23541 Référence CVE CVE-2022-29162 https://www.cve.org/CVERecord?id=CVE-2022-29162 Référence CVE CVE-2022-31116 https://www.cve.org/CVERecord?id=CVE-2022-31116 Référence CVE CVE-2022-31117 https://www.cve.org/CVERecord?id=CVE-2022-31117 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2023-23934 https://www.cve.org/CVERecord?id=CVE-2023-23934 Référence CVE CVE-2023-25577 https://www.cve.org/CVERecord?id=CVE-2023-25577 Référence CVE CVE-2023-25809 https://www.cve.org/CVERecord?id=CVE-2023-25809 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-27561 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0350Multiples vulnérabilités dans les produits IBM

Bulletin de sécurité IBM 7149294 du 23 avril 2024 https://www.ibm.com/support/pages/node/7149294 Référence CVE CVE-2017-11468 https://www.cve.org/CVERecord?id=CVE-2017-11468 Référence CVE CVE-2021-32760 https://www.cve.org/CVERecord?id=CVE-2021-32760 Référence CVE CVE-2021-41103 https://www.cve.org/CVERecord?id=CVE-2021-41103 Référence CVE CVE-2021-43784 https://www.cve.org/CVERecord?id=CVE-2021-43784 Référence CVE CVE-2021-43816 https://www.cve.org/CVERecord?id=CVE-2021-43816 Référence CVE CVE-2022-23471 https://www.cve.org/CVERecord?id=CVE-2022-23471 Référence CVE CVE-2022-23648 https://www.cve.org/CVERecord?id=CVE-2022-23648 Référence CVE CVE-2022-29162 https://www.cve.org/CVERecord?id=CVE-2022-29162 Référence CVE CVE-2022-31030 https://www.cve.org/CVERecord?id=CVE-2022-31030 Référence CVE CVE-2022-42969 https://www.cve.org/CVERecord?id=CVE-2022-42969 Référence CVE CVE-2023-2253 https://www.cve.org/CVERecord?id=CVE-2023-2253 Référence CVE CVE-2023-25153 https://www.cve.org/CVERecord?id=CVE-2023-25153 Référence CVE CVE-2023-25173 https://www.cve.org/CVERecord?id=CVE-2023-25173 Référence CVE CVE-2023-25809 https://www.cve.org/CVERecord?id=CVE-2023-25809 Référence CVE CVE-2023-26136 https://www.cve.org/CVERecord?id=CVE-2023-26136 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CV

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0119Multiples vulnérabilités dans les produits Siemens

ecord?id=CVE-2022-23521 Référence CVE CVE-2022-24834 https://www.cve.org/CVERecord?id=CVE-2022-24834 Référence CVE CVE-2022-2586 https://www.cve.org/CVERecord?id=CVE-2022-2586 Référence CVE CVE-2022-26691 https://www.cve.org/CVERecord?id=CVE-2022-26691 Référence CVE CVE-2022-28737 https://www.cve.org/CVERecord?id=CVE-2022-28737 Référence CVE CVE-2022-28738 https://www.cve.org/CVERecord?id=CVE-2022-28738 Référence CVE CVE-2022-28739 https://www.cve.org/CVERecord?id=CVE-2022-28739 Référence CVE CVE-2022-2880 https://www.cve.org/CVERecord?id=CVE-2022-2880 Référence CVE CVE-2022-29154 https://www.cve.org/CVERecord?id=CVE-2022-29154 Référence CVE CVE-2022-29162 https://www.cve.org/CVERecord?id=CVE-2022-29162 Référence CVE CVE-2022-29187 https://www.cve.org/CVERecord?id=CVE-2022-29187 Référence CVE CVE-2022-29536 https://www.cve.org/CVERecord?id=CVE-2022-29536 Référence CVE CVE-2022-29862 https://www.cve.org/CVERecord?id=CVE-2022-29862 Référence CVE CVE-2022-32148 https://www.cve.org/CVERecord?id=CVE-2022-32148 Référence CVE CVE-2022-3294 https://www.cve.org/CVERecord?id=CVE-2022-3294 Référence CVE CVE-2022-3437 https://www.cve.org/CVERecord?id=CVE-2022-3437 Référence CVE CVE-2022-34903 https://www.cve.org/CVERecord?id=CVE-2022-34903 Référence CVE CVE-2022-34918 https://www.cve.org/CVERecord?id=CVE-

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.
Patch available
Affected
SCALANCE XCH328 (6GK5328-4TS01-2EC2); SCALANCE XCM324 (6GK5324-8TS01-2AC2); SCALANCE XCM328 (6GK5328-4TS01-2AC2); SCALANCE XCM332 (6GK5332-0GA01-2AC2); SCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3); SCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3); SCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3); SCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3); SCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3); SCALANCE XRM334 (2x230 V AC, 12xFO) (6GK5334-3TS01-4AR3); SCALANCE XRM334 (2x230 V AC, 8xFO) (6GK5334-2TS01-4AR3)
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
Update to V2.4 or later version
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 17 May 2022 · Last source change 23 Apr 2025, 18:25 UTC · CWE-276 · Incorrect Default Permissions

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-3675
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
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-3675↗Vendor CSAF · Siemens ProductCERT↗Patch or update reference↗CVE authority or vendor reference↗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-29162 · cve.blacktree.nl