Security readout for executives and security teams
Plain-English summary
An authorized user could crash KubeEdge CloudHub by causing it to read an excessively large request body into memory. The business impact is service interruption for edge orchestration environments using affected versions with CloudHub enabled, not data theft or privilege escalation.
Executive priority
Treat this as a targeted availability risk for KubeEdge edge environments. Patch during the next operationally safe maintenance window, sooner if CloudHub is broadly accessible or edge service availability is business-critical.
Technical view
CVE-2022-31075 is a CWE-400 resource consumption flaw in KubeEdge CloudHub handling of EdgeCore CSR signing through /edge.crt. Affected versions before 1.9.4, 1.10.2, and 1.11.1 can exhaust memory and crash the HTTP service when CloudHub is enabled.
Likely exposure
Exposure is limited to KubeEdge deployments running affected versions with the CloudHub module enabled in cloudcore.yaml. Sources state the request must pass authorization, so the likely attacker is an authorized user or compromised authorized identity with CloudHub access.
Exploitation context
The provided sources do not report active exploitation, and this CVE is not marked KEV. Exploitation requires CloudHub reachability and successful authorization. The impact is denial of service through memory exhaustion, with no sourced confidentiality or integrity impact.
Researcher notes
Root cause is unbounded request body handling that reads data into memory during EdgeCore CSR signing. Scope depends on CloudHub being enabled. The CVSS vector has network access, low complexity, high privileges required, no user interaction, and high availability impact only.
Mitigation direction
- Upgrade KubeEdge to 1.11.1, 1.10.2, 1.9.4, or later maintained versions.
- If immediate upgrade is impossible, disable the CloudHub switch in cloudcore.yaml as the vendor workaround.
- Review vendor guidance before applying alternative compensating controls.
- Prioritize environments where CloudHub is reachable by many authorized users.
Validation and detection
- Inventory KubeEdge versions and flag deployments matching the affected version ranges.
- Check cloudcore.yaml to confirm whether the CloudHub module is enabled.
- Verify upgrade status against fixed versions 1.11.1, 1.10.2, or 1.9.4.
- Review CloudHub availability and memory-related crash logs around /edge.crt access.
- Confirm CloudHub authorization scope is limited to expected users and services.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31075 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H1.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.9MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/kubeedge/kubeedge/security/advisories/GHSA-x3px-2p95-f6jrCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.