dbcve.org
KubeedgeWeb browser · Linuxfoundation

CVE-2022-31079

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-11
Fix available
A fix is available. Upgrade to 1.9.4 / 1.10.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. Prior to versions 1.11.1, 1.10.2, and 1.9.4, the Cloud Stream server and the Edge Stream server reads the entire message into memory without imposing a limit on the size of this message. An attacker can exploit this by sending a large message to exhaust memory and cause a DoS. The Cloud Stream server and the Edge Stream server are under DoS attack in this case. The consequence of the exhaustion is that the CloudCore and EdgeCore will be in a denial of service. Only an authenticated user can cause this issue. It will be affected only when users enable `cloudStream` module in the config file `cloudcore.yaml` and enable `edgeStream` module in the config file `edgecore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable cloudStream module in the config file `cloudcore.yaml` and disable edgeStream module in the config file `edgecore.yaml`.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

KubeEdge Cloud Stream server and Edge Stream server lack message size limits, allowing authenticated attackers to send arbitrarily large messages that exhaust memory and cause denial of service. The vulnerability only affects deployments with cloudStream module enabled in cloudcore.yaml and edgeStream module enabled in edgecore.yaml.

MitigationUpgrade to KubeEdge versions 1.11.1, 1.10.2, or 1.9.4, or disable the cloudStream and edgeStream modules in their respective configuration files as a workaround.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KubeedgeWeb browser
Affected:< 1.9.4>= 1.10.0, < 1.10.2>= 1.11.0, < 1.11.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check KubeEdge version
    Run 'kubeedge --version' or check the version of the cloudcore/edgecore binaries installed in your environment
    Affected if Version is less than 1.9.4, or between 1.10.0 (inclusive) and 1.10.2 (exclusive), or between 1.11.0 (inclusive) and 1.11.1 (exclusive)
  2. Locate cloudcore.yaml
    Find the cloudcore.yaml configuration file, typically in /etc/kubeedge/ or the directory where cloudcore configuration is stored
    Affected if File exists and cloudStream module configuration is present
  3. Verify cloudStream module status
    Open cloudcore.yaml and search for the 'cloudStream' module entry. Check if it is set to 'true' or enabled in the modules section
    Affected if cloudStream module is enabled (set to true or present as enabled)
  4. Locate edgecore.yaml
    Find the edgecore.yaml configuration file on edge nodes, typically in /etc/kubeedge/ or the edge node configuration directory
    Affected if File exists and edgeStream module configuration is present
  5. Verify edgeStream module status
    Open edgecore.yaml and search for the 'edgeStream' module entry. Check if it is set to 'true' or enabled in the modules section
    Affected if edgeStream module is enabled (set to true or present as enabled)

You are affected if your KubeEdge version falls within the vulnerable ranges AND both the cloudStream module in cloudcore.yaml and the edgeStream module in edgecore.yaml are enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.4 / 1.10.2 / 1.11.1 or later
Fixed in 1.9.41.10.21.11.1
Interim mitigation

Upgrade to KubeEdge versions 1.11.1, 1.10.2, or 1.9.4, or disable the cloudStream and edgeStream modules in their respective configuration files as a workaround.

Recommended fix High confidence

Upgrade to KubeEdge 1.9.4, 1.10.2, or 1.11.1 (or later stable release) depending on current version

  1. 1. Identify current KubeEdge version by running `kubeedge version` or checking the version of installed CloudCore and EdgeCore.
  2. 2. Determine the appropriate upgrade target based on current version: if running < 1.9.4, upgrade to 1.9.4; if running >= 1.10.0 and < 1.10.2, upgrade to 1.10.2; if running >= 1.11.0 and < 1.11.1, upgrade to 1.11.1.
  3. 3. For production environments, upgrade to the latest stable release (1.11.1 or later) to get all security fixes.
  4. 4. Follow the standard KubeEdge upgrade documentation for your deployment type (single-node or cluster).
  5. 5. After upgrade, verify CloudCore and EdgeCore services are running: `systemctl status cloudcore` and `systemctl status edgecore`.
  6. 6. Verify the fix by checking that the Stream servers now enforce message size limits.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kubeedge Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31079 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data