Skip to main content
No exploitation reportedFix available

CVE-2022-31075

No exploitation reported by the sources we read.

  • Published2022-07-11
  • Fixed in1.11.1 · 1.10.2 · 1.9.4
  • WeaknessCWE-400 · CWE-770

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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, EdgeCore may be susceptible to a DoS attack on CloudHub if an attacker was to send a well-crafted HTTP request to `/edge.crt`. If an attacker can send a well-crafted HTTP request to CloudHub, and that request has a very large body, that request can crash the HTTP service through a memory exhaustion vector. The request body is being read into memory, and a body that is larger than the available memory can lead to a successful attack. Because the request would have to make it through authorization, only authorized users may perform this attack. The consequence of the exhaustion is that CloudHub will be in denial of service. KubeEdge is affected only when users enable the CloudHub module in the file `cloudcore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable the CloudHub switch in the config file `cloudcore.yaml`.

Timeline

dates in UTC
  1. 2022-07-1121:15CVE publishedNVD

Versions per branch

NVD · OSV
Linuxfoundation kubeedge
BranchAffectedFixed in
1.11≥ 1.11.0, < 1.11.11.11.1
1.10≥ 1.10.0, < 1.10.21.10.2
1.9< 1.9.41.9.4

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • kubeedge
    Affected
    • = < 1.9.4no fix stated
    • = >= 1.10.0, < 1.10.2no fix stated
    • = = 1.11.0no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2022-07-11

Fix

  1. Update Linuxfoundation kubeedge to 1.11.1 · 1.10.2 · 1.9.4

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2025-04-23
  • CNACVSS 3.14.9known since 2026-10-23
  • NVDCVSS 3.16.5read 2026-10-23
  • NVDCVSS 2.03.5read 2026-10-23
  • CNAweakness (CWE)CWE-400known since 2026-10-23
  • NVDweakness (CWE)CWE-770read 2026-10-23
  • FIRST EPSSEPSS score1.0 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2022-07-11

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Published
2022-07-11
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-x3px-2p95-f6jr

Frequently asked questions

What is CVE-2022-31075?

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, EdgeCore may be susceptible to a DoS attack on CloudHub if an attacker was to send a well-crafted HTTP request to `/edge.crt`. If an attacker can send a well-crafted HTTP request to CloudHub, and that request has a very large body, that request can crash the HTTP service through a memory exhaustion vector. The request body is being read into memory, and a body that is larger than the available memory can lead to a successful attack. Because the request would have to make it through authorization, only authorized users may perform this attack. The consequence of the exhaustion is that CloudHub will be in denial of service. KubeEdge is affected only when users enable the CloudHub module in the file `cloudcore.yaml`. This bug has been fixed in Kubeedge 1.11.1, 1.10.2, and 1.9.4. As a workaround, disable the CloudHub switch in the config file `cloudcore.yaml`.

Is CVE-2022-31075 actively exploited?

Active exploitation of CVE-2022-31075 has not been confirmed. Its EPSS score was 1.0% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-31075?

CVE-2022-31075 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Running kubeedge/kubeedge? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record