What is CVE-2022-31076?A medium-severity flaw in Kubeedge, explained.
CVE-2022-31076 is a medium-severity flaw (CVSS 5.7) in Kubeedge from Linuxfoundation, published on 27 June 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 0.6%. If you run an affected version, plan in the vendor’s fix.
Published 27 June 2022. Record last updated 7 July 2022. We keep this page's data up to date.
What is CVE-2022-31076? In plain terms.
An attacker has to be on the same local network with an ordinary user account, and nobody has to click anything. If it works, the attacker can take it offline.
KubeEdge is built upon Kubernetes and extends native containerized application orchestration and device management to hosts at the Edge. In affected versions a malicious message can crash CloudCore by triggering a nil-pointer dereference in the UDS Server. Since the UDS Server only communicates with the CSI Driver on the cloud side, the attack is limited to the local host network. As such, an attacker would already need to be an authenticated user of the Cloud. Additionally it will be affected only when users turn on the unixsocket switch in the config file cloudcore.yaml. This bug has been fixed in Kubeedge 1.11.0, 1.10.1, and 1.9.3. Users should update to these versions to resolve the issue. Users unable to upgrade should sisable the unixsocket switch of CloudHub in the config file cloudcore.yaml.
What kind of flaw is it?
- CWE-476NULL Pointer Dereference
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beOn the same local network
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn ordinary user account
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan take it offline
Severity vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is CVE-2022-31076 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 0.6%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2022-31076 scores 40. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isKey context
- Real threat activity around itKey context
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2022-31076 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2022-31076? One product.
The published record lists 1 product from 1 vendor. Versions are shown as published: "before 1.9.3" means every version up to, but not including, 1.9.3. If you run one of these, check your version, then go to the fix below.
- Application
Kubeedge
Affected versionsbefore 1.9.31.10.0-beta01.10.0
How do I fix CVE-2022-31076? Four steps.
- Check whether you run itCompare 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.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack 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.
Does CVE-2022-31076 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
KubeEdge is built upon Kubernetes and extends native containerized application orchestration and device management to hosts at the Edge. In affected versions...
- Matched to
- Kubeedge on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2022-31076 is a medium-severity flaw in Kubeedge from Linuxfoundation, published on 27 June 2022. An attacker has to be on the same local network with an ordinary user account, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 5.7 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2022-31076 is 40 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.
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 0.6%. That can change at any time, which is why we keep watching.
For Kubeedge from Linuxfoundation: before 1.9.3, 1.10.0-beta0, 1.10.0.
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.