Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-3294

Node address isn't always verified when proxying

Description

Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this validation could allow authenticated requests destined for Nodes to to the API server's private network.

Timeline

  1. ID reserved

    By kubernetes

  2. · 5 months later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-3294, by who scored it
Scored byCVSSScoreVector
kubernetesCNA (assigner)3.1Medium6.6CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
1.6% · top 24% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.6.

Affected products

  • Kubernetes · Kubernetes

    • affected unspecified – ≤ v1.25.3
    • affected unspecified – ≤ v1.24.7
    • affected unspecified – ≤ v1.23.13
    • affected unspecified – ≤ v1.22.15

Affected packages

From reviewed advisories of the GitHub Advisory Database.

What to do

Workaround: Configuring an egress proxy for egress to the cluster network can mitigate this vulnerability

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-3294 badge
[![CVE-2022-3294](https://cveledger.app/badge/CVE-2022-3294.svg)](https://cveledger.app/cve/CVE-2022-3294)

Record last updated .