CVE-2018-10021059.8CriticalCWE-388

CVE-2018-1002105: Kubernetes vulnerability

Kubernetes

Vendor fix available · Affected: Kubernetes · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

87.0%probability of exploitation in the next 30 days

99th percentile

050100

Higher than 99% of scored CVEs

9.8CriticalCVSS 3.0

LowMediumHighCrit.

DescriptionCVE.org

In 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 kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

Kubernetes · Kubernetesv1.0.x; v1.1.x; v1.2.x; v1.3.x; v1.4.x; v1.5.x and 7 more

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Error Handling · Other weaknesses
Vendor: Kubernetes
Published: December 2018
Band: Likely to be exploited (10% or more), December 2018

CoverageNo articles yet

No CyberSIXT article names CVE-2018-1002105 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

8 more references are in the CVE record.