CVE-2022-31079: GO-2022-0511 - KubeEdge Cloud Stream and Edge Stream DoS from large stream message in github.com/kubeedge/kubeedge

CVE-2022-31079 · Severity: low · CVSS 3.1 · Published 2024-08-21

KubeEdge Cloud Stream and Edge Stream DoS from large stream message in github.com/kubeedge/kubeedge

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

Quick answers

Is CVE-2022-31079 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-31079 being exploited in the wild.
How severe is CVE-2022-31079?
Low severity, with a CVSS score of 3.1, published 21 August 2024.
Which products and versions are affected?
github.com/kubeedge/kubeedge (Go) SEMVER:introduced=0,fixed=1.9.4,introduced=1.10.0,fixed=1.10.2,introduced=1.11.0,fixed=1.11.1, SEMVER:introduced=1.11.0,fixed=1.11.1.
Is there a fix for CVE-2022-31079?
Yes. github.com/kubeedge/kubeedge (Go): upgrade to 1.11.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-31079?
Check whether you run github.com/kubeedge/kubeedge (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/kubeedge/kubeedge (Go): upgrade to 1.11.1 or later
    go get github.com/kubeedge/kubeedge@v1.11.1

Affected products

  • github.com/kubeedge/kubeedge (Go) SEMVER:introduced=0,fixed=1.9.4,introduced=1.10.0,fixed=1.10.2,introduced=1.11.0,fixed=1.11.1, SEMVER:introduced=1.11.0,fixed=1.11.1

Identifiers

  • CVE-2022-31079
  • GHSA-wrcr-x4qj-j543
  • GO-2022-0511

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