CVE-2016-9962: GO-2022-0835 - Information Exposure in RunC in github.com/opencontainers/runc

CVE-2016-9962 · Severity: low · CVSS 3 · Published 2024-08-21

Information Exposure in RunC in github.com/opencontainers/runc

Technologies: github.com/opencontainers/runc (Go). Vendors: Go.

Quick answers

Is CVE-2016-9962 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-9962 being exploited in the wild.
How severe is CVE-2016-9962?
Low severity, with a CVSS score of 3, published 21 August 2024.
Which products and versions are affected?
github.com/opencontainers/runc (Go) SEMVER:introduced=0,fixed=1.0.0-rc3.
Is there a fix for CVE-2016-9962?
Yes. github.com/opencontainers/runc (Go): upgrade to 1.0.0-rc3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2016-9962?
Check whether you run github.com/opencontainers/runc (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/opencontainers/runc (Go): upgrade to 1.0.0-rc3 or later
    go get github.com/opencontainers/runc@v1.0.0-rc3

Affected products

  • github.com/opencontainers/runc (Go) SEMVER:introduced=0,fixed=1.0.0-rc3

Identifiers

  • CVE-2016-9962
  • GHSA-gp4j-w3vj-7299
  • GO-2022-0835

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.