Skip to content
Fencer Intel
medium 6.5

CVE-2020-1701 json

Permissions bypass in KubeVirt

published 5y ago modified 4mo ago also GHSA-849r-8wvp-4wwg , GO-2024-2765 , EUVD-2021-1288

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

A flaw was found in the KubeVirt main virt-handler versions before 0.26.0 regarding the access permissions of virt-handler. An attacker with access to create VMs could attach any secret within their namespace, allowing them to read the contents of that secret.

Patch / fix

  • go kubevirt.io/kubevirt 0.26.0
  • kubevirt kubevirt 0.26.0

Is CVE-2020-1701 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-1701 updated cvss 6.5

virt-handler: virt-handler daemonset clusterroles allows retrieval of secrets

  • Red Hat OpenShift Virtualization 1 virt-handler
    affected: workaround, no fix available “Fix deferred”
  • Red Hat OpenShift Virtualization 2 virt-handler-container
    affected: workaround, no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go kubevirt.io/kubevirt
<0.26.0
0.26.0

Affected products

  • n/a virt-handler

Classification

Weakness
  • CWE-732 Incorrect Permission Assignment for Critical Resource

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.