Skip to content
Noroxi
CVE-2022-3294· NVD / CVE Program· CNA kubernetes

Node address isn't always verified when proxying

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.

HighCVSS 8.8 · v3.1—Proof of concept Fix available
Published
Mar 1, 2023
Updated
Jun 17, 2026
EPSS
1.6% · 75th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · kubernetes
6.6
2.2 point gap

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
kuberneteskubernetes

Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)

Add to my stack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • kubernetes kubernetesbefore 1.22.16
  • kubernetes kubernetes1.23.0 and later · before 1.23.14
  • kubernetes kubernetes1.24.0 and later · before 1.24.8
  • kubernetes kubernetes1.25.0 and later · before 1.25.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.

  • Kubernetes Kubernetes

    • unspecified and later · up to and including v1.25.3affected
    • unspecified and later · up to and including v1.24.7affected
    • unspecified and later · up to and including v1.23.13affected
    • unspecified and later · up to and including v1.22.15affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12kubernetesbefore 1.20.5+really1.20.2-11.20.5+really1.20.2-1
Gogithub.com/kubernetes/kubernetesfrom 1.22.0 · before 1.22.161.22.16
Gogithub.com/kubernetes/kubernetesfrom 1.23.0 · before 1.23.141.23.14
Gogithub.com/kubernetes/kubernetesfrom 1.24.0 · before 1.24.81.24.8
Gogithub.com/kubernetes/kubernetesfrom 1.25.0 · before 1.25.41.25.4
Gok8s.io/kubernetesfrom 1.22.0 · before 1.22.161.22.16
Gok8s.io/kubernetesfrom 1.23.0 · before 1.23.141.23.14
Gok8s.io/kubernetesfrom 1.24.0 · before 1.24.81.24.8
Gok8s.io/kubernetesfrom 1.25.0 · before 1.25.41.25.4
openSUSE:Tumbleweedkubernetes1.25before 1.25.7-1.11.25.7-1.1
Red Hat:openshift:4.12::el8microshiftbefore 0:4.12.1-202301261525.p0.g3db9e81.assembly.4.12.1.el80:4.12.1-202301261525.p0.g3db9e81.assembly.4.12.1.el8
SUSE:Linux Enterprise Module for Containers 15 SP4kubernetes1.23before 1.23.17-150300.7.6.11.23.17-150300.7.6.1

Other highest-scoring records for the same primary product.

  • CVE-2018-1002105In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the
    65This week
  • CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port
    55Plan
  • CVE-2017-1002101In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with
    42Plan
  • CVE-2018-1002101In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Wi
    40Plan
  • CVE-2017-1000056Kubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin resulting in the ability to
    40Plan
  • CVE-2016-1906Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:kubernetes1.20.5+really1.20.2-1 · Debian:12Package registry (OSV)
Go:github.com/kubernetes/kubernetes1.22.16Package registry (OSV)
Go:github.com/kubernetes/kubernetes1.23.14Package registry (OSV)
Go:github.com/kubernetes/kubernetes1.24.8Package registry (OSV)
Go:github.com/kubernetes/kubernetes1.25.4Package registry (OSV)
Go:k8s.io/kubernetes1.22.16Package registry (OSV)
Go:k8s.io/kubernetes1.23.14Package registry (OSV)
Go:k8s.io/kubernetes1.24.8Package registry (OSV)
Go:k8s.io/kubernetes1.25.4Package registry (OSV)
opensuse:kubernetes1.251.25.7-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:microshift0:4.12.1-202301261525.p0.g3db9e81.assembly.4.12.1.el8 · Red Hat:openshift:4.12::el8Package registry (OSV)
suse:kubernetes1.231.23.17-150300.7.6.1 · SUSE:Linux Enterprise Module for Containers 15 SP4Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-01-14

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+1049 d
  3. TodaySep 30, 2026+1309 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records