CVE-2024-36620: GO-2024-3311 - NULL Pointer Dereference on moby image history in github.com/moby/moby

CVE-2024-36620 · Severity: low · CVSS 3.1 · Published 2024-12-09

NULL Pointer Dereference on moby image history in github.com/moby/moby

Technologies: github.com/moby/moby (Go). Vendors: Go.

Quick answers

Is CVE-2024-36620 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-36620 being exploited in the wild.
How severe is CVE-2024-36620?
Low severity, with a CVSS score of 3.1, published 9 December 2024.
Which products and versions are affected?
github.com/moby/moby (Go) SEMVER:introduced=25.0.0,fixed=26.1.0, SEMVER:introduced=25.0.0+incompatible,fixed=26.1.0+incompatible.
Is there a fix for CVE-2024-36620?
Yes. github.com/moby/moby (Go): upgrade to 26.1.0, 26.1.0+incompatible or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-36620?
Check whether you run github.com/moby/moby (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/moby/moby (Go): upgrade to 26.1.0, 26.1.0+incompatible or later
    go get github.com/moby/moby@v26.1.0+incompatible

Affected products

  • github.com/moby/moby (Go) SEMVER:introduced=25.0.0,fixed=26.1.0, SEMVER:introduced=25.0.0+incompatible,fixed=26.1.0+incompatible

Identifiers

  • CVE-2024-36620
  • GHSA-q59j-vv4j-v33c
  • GO-2024-3311

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