# What is CVE-2022-31073?

> CVE-2022-31073 is a high-severity flaw (CVSS 7.5) in Kubeedge from Linuxfoundation, published on 11 July 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.7%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2022-31073

## At a glance

- **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle.
- **Precursor Intelligence risk score:** 48 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes.
- **Severity:** High (CVSS 7.5 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 1.7% (latest exploit-likelihood forecast)
- **Published:** 11 July 2022
- **Record last updated:** 16 July 2022
- **Main product:** Kubeedge from Linuxfoundation
- **Affected products:** 1

## What is CVE-2022-31073? In plain terms

It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.

### The official 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, the ServiceBus server on the edge side may be susceptible to a DoS attack if an HTTP request containing a very large Body is sent to it. It is possible for the node to be exhausted of memory. The consequence of the exhaustion is that other services on the node, e.g. other containers, will be unable to allocate memory and thus causing a denial of service. Malicious apps accidentally pulled by users on the host and have the access to send HTTP requests to localhost may make an attack. It will be affected only when users enable the `ServiceBus` 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 the `ServiceBus` module in the config file `edgecore.yaml`.

### What kind of flaw is it?

- CWE-400: Uncontrolled Resource Consumption

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can take it offline

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

## Is CVE-2022-31073 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.7%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 1.7%, 1.7%, 1.7%, 1.7%, 1.7%, 1.7%, 1.7%.

### Timeline

- 11 July 2022: Published
- 16 July 2022: Record last updated

### How Precursor Intelligence ranks it

CVE-2022-31073 scores **48 out of 100 (Medium)**, with the action "Plan remediation".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: key context
- Real threat activity around it: key context

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2022-31073?

The published record lists 1 product. Versions are as published: "before 1.9.4" means every version up to, but not including, 1.9.4.

- [Kubeedge](https://www.precursorintelligence.com/product/linuxfoundation/kubeedge) by [Linuxfoundation](https://www.precursorintelligence.com/vendors/linuxfoundation) (Application): before 1.9.4, 1.10.0 to before 1.10.2, 1.11.0 to before 1.11.1

## How do I fix CVE-2022-31073?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [github.com](https://github.com/kubeedge/kubeedge/pull/4038) (Issue tracking, Patch, Third-party advisory)
- [github.com](https://github.com/kubeedge/kubeedge/pull/4039) (Issue tracking, Patch, Third-party advisory)
- [github.com](https://github.com/kubeedge/kubeedge/pull/4042) (Issue tracking, Patch, Third-party advisory)
- [github.com](https://github.com/kubeedge/kubeedge/security/advisories/GHSA-vwm6-qc77-v2rh) (Exploit, Third-party advisory)

## Questions

### What is CVE-2022-31073?

CVE-2022-31073 is a high-severity flaw in Kubeedge from Linuxfoundation, published on 11 July 2022. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.

### How serious is CVE-2022-31073?

It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2022-31073 is 48 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

### Is CVE-2022-31073 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.7%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2022-31073 affect?

For Kubeedge from Linuxfoundation: before 1.9.4, 1.10.0 to before 1.10.2, 1.11.0 to before 1.11.1.

### How do I fix CVE-2022-31073?

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2022-31073 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact