Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

io.fabric8:kubernetes-client

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.7MavenPublished

    fabric8 kubernetes-client vulnerable

    CVE-2021-4178 · GHSA-98g7-rxmf-rrxm

    Affected
    • Maven io.fabric8:kubernetes-client >= 5.0.0-beta-1, < 5.0.3; >= 5.1.0, < 5.1.2; >= 5.2.0, < 5.3.2; >= 5.5.0, < 5.7.4; >= 5.8.0, < 5.8.1; >= 5.9.0, < 5.10.2; >= 5.11.0, < 5.11.2
    Fixed in
    5.3.25.11.25.10.25.7.45.0.35.1.25.8.1· Vendor fix available
    Issue
    fabric8 Kubernetes client had an arbitrary code execution flaw in versions 5.0.0-beta-1 and higher. Attackers could potentially insert malicious YAMLs due to misconfigured YAML parsing.

    Recommended action: Upgrade to 5.11.2, 5.10.2, 5.8.1 or 4 more by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.4MavenPublished

    Improper Limitation of a Pathname to a Restricted Directory in Fabric8 Kubernetes Client

    CVE-2021-20218 · GHSA-jwh2-ffg4-48xc

    Affected
    • Maven io.fabric8:kubernetes-client >= 4.2.0, <= 4.7.1; >= 4.8.0, <= 4.11.1; >= 4.12.0, <= 4.13.1; >= 5.0.0, <= 5.0.1
    Fixed in
    4.11.24.13.24.7.25.0.2· Vendor fix available
    Issue
    A flaw was found in the fabric8 kubernetes-client in version 4.2.0 and after. This flaw allows a malicious pod/container to cause applications using the fabric8 kubernetes-client copy command to extract files outside the working path. The highest threat from this vulnerability is to integrity and system availability. This has been fixed in kubernetes-client-4.13.2 kubernetes-client-5.0.2 kubernetes-client-4.11.2 kubernetes-client-4.7.2

    Recommended action: Upgrade to 5.0.2, 4.13.2, 4.11.2 or 4.7.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →