GHSA-c9cp-9c75-9v8c: Github.com/containerd/containerd Containerd Started With Non-empty Inheritable Vulnerability

LOW
Published
Advisory Summary

GHSA-c9cp-9c75-9v8c is a LOW containerd started with non-empty inheritable vulnerability (General Security Weakness) affecting Github.com/containerd/containerd libraries in the Go ecosystem. The issue involves containerd started with non-empty inheritable linux process capabilities. Remediation is available by upgrading affected packages to version 1.5.11, 1.6.2.

GHSA-c9cp-9c75-9v8c at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-c9cp-9c75-9v8c
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Github.com/containerd/containerd
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-c9cp-9c75-9v8c

To remediate this vulnerability, upgrade all affected Github.com/containerd/containerd dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/containerd/containerd fixed: 1.5.11
Upgrade github.com/containerd/containerd to 1.5.11
github.com/containerd/containerd fixed: 1.6.2
Upgrade github.com/containerd/containerd to 1.6.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/containerd/containerd

How to Check if You Are Affected

To determine whether your application is affected by GHSA-c9cp-9c75-9v8c, inspect your project dependencies for Github.com/containerd/containerd:

inspect dependencies for github.com/containerd/containerd

Analyze the terminal output to locate any version of Github.com/containerd/containerd in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.5.11), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Github.com/containerd/containerd, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact A bug was found in containerd where containers were incorrectly started 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)`. Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set. Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set. Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted. 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. ### Patches This bug has been fixed in containerd 1.5.11 and 1.6.2. Users should update to these versions as soon as possible. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes containerd behavior such that containers are started with a more typical Linux environment. Refer to `capabilities(7)` for a description of how capabilities work. Note that permitted file capabilities continue to allow for privileges to be raised up to the container's bounding set and that processes may add capabilities to their own inheritable set up to the container's bounding set per the rules described in the manual page. In all cases the container's bounding set provides an upper bound on the capabilities that can be assumed and provides for the container security sandbox. ### Workarounds The entrypoint of a container can be modified to use a utility like `capsh(1)` to drop inheritable capabilities prior to the primary process starting. ### For more information If you have any questions or comments about this advisory: * [Open an issue](https://github.com/containerd/containerd/issues/new) * Email us at [security@containerd.io](mailto:security@containerd.io) if you think you’ve found a security bug

GHSA-c9cp-9c75-9v8c Affected Github.com/containerd/containerd Versions

2 component(s)
Fixed Versions:
1.5.111.6.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/containerd/containerd
Go
< 1.5.11
1.5.11
github.com/containerd/containerd
Go
≥ 1.6.0
< 1.6.2
1.6.2

References

Frequently Asked Questions

What is GHSA-c9cp-9c75-9v8c?
GHSA-c9cp-9c75-9v8c is a security vulnerability in Github.com/containerd/containerd involving containerd started with non-empty inheritable Linux process capabilities under General Security Weakness.
Which Github.com/containerd/containerd versions are affected?
Affected versions include releases prior to 1.5.11, 1.6.2 across affected packages: github.com/containerd/containerd.
What version fixes GHSA-c9cp-9c75-9v8c?
Upgrading to 1.5.11, 1.6.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/containerd/containerd affected?
Yes, github.com/containerd/containerd is affected in releases prior to 1.5.11, 1.6.2. Upgrade your dependency to 1.5.11, 1.6.2 or later.
What CWE is associated with GHSA-c9cp-9c75-9v8c?
GHSA-c9cp-9c75-9v8c is classified under General Security Weakness.
How can I check Go dependencies for GHSA-c9cp-9c75-9v8c?
Run the dependency tree command: 'inspect dependencies for github.com/containerd/containerd'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-c9cp-9c75-9v8c",
  "modified" : "2024-07-08T12:58:29Z",
  "published" : "2024-05-14T22:04:56Z",
  "aliases" : [ ],
  "summary" : "containerd started with non-empty inheritable Linux process capabilities",
  "details" : "### Impact\n\nA bug was found in containerd where containers were incorrectly started 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)`.  Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set.  Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set.  Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted.\n\nThis 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.\n\n\n### Patches\n\nThis bug has been fixed in containerd 1.5.11 and 1.6.2.  Users should update to these versions as soon as possible.  Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset.\n\nThis fix changes containerd behavior such that containers are started with a more typical Linux environment.  Refer to `capabilities(7)` for a description of how capabilities work.  Note that permitted file capabilities continue to allow for privileges to be raised up to the container's bounding set and that processes may add capabilities to their own inheritable set up to the container's bounding set per the rules described in the manual page.  In all cases the container's bounding set provides an upper bound on the capabilities that can be assumed and provides for the container security sandbox.\n\n### Workarounds\n\nThe entrypoint of a container can be modified to use a utility like `capsh(1)` to drop inheritable capabilities prior to the primary process starting.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* [Open an issue](https://github.com/containerd/containerd/issues/new)\n* Email us at [security@containerd.io](mailto:security@containerd.io) if you think you’ve found a security bug",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/containerd/containerd"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.5.11"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/containerd/containerd"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.6.0"
      }, {
        "fixed" : "1.6.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/containerd/containerd/security/advisories/GHSA-c9cp-9c75-9v8c"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/containerd/containerd/commit/e9af808591ee1468f9b0ad6a0d41fdf93ee0c1bc"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/containerd/containerd"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-05-14T22:04:56Z",
    "nvd_published_at" : null
  }
}