BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2018
CVE-2018-1002105High confidence

Kubernetes: security vulnerability

Kubernetes · Kubernetes

9.8CriticalCVSS 3.0
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 86.98% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Kubernetes Kubernetes and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcekubernetesVendor fix publishedDebian records a fixed source-package version for this release.1.17.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcekubernetesVendor fix publishedDebian records a fixed source-package version for this release.1.17.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcekubernetesVendor fix publishedDebian records a fixed source-package version for this release.1.17.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcekubernetesVendor fix publishedDebian records a fixed source-package version for this release.1.17.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-0831

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-388 ↗

CWE-388. Open the MITRE definition for the exact weakness description.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-388Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2022-0510IBM DB2: Mehrere Schwachstellen

Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in IBM DB2 ausnutzen, um Dateien zu manipulieren, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen, willkürlichen Code mit erhöhten Rechten auszuführen, Informationen falsch darzustellen und beliebigen Code auszuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-591Multiples vulnérabilités dans les produits IBM

distance et un contournement de la politique de sécurité. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité IBM 6596399 du 29 juin 2022 https://www.ibm.com/support/pages/node/6596399 Bulletin de sécurité IBM 6596971 du 29 juin 2022 https://www.ibm.com/support/pages/node/6596971 Bulletin de sécurité IBM 6599703 du 29 juin 2022 https://www.ibm.com/support/pages/node/6599703 Référence CVE CVE-2017-1002101 https://www.cve.org/CVERecord?id=CVE-2017-1002101 Référence CVE CVE-2017-18367 https://www.cve.org/CVERecord?id=CVE-2017-18367 Référence CVE CVE-2018-1002105 https://www.cve.org/CVERecord?id=CVE-2018-1002105 Référence CVE CVE-2018-1098 https://www.cve.org/CVERecord?id=CVE-2018-1098 Référence CVE CVE-2018-1099 https://www.cve.org/CVERecord?id=CVE-2018-1099 Référence CVE CVE-2018-16886 https://www.cve.org/CVERecord?id=CVE-2018-16886 Référence CVE CVE-2018-17142 https://www.cve.org/CVERecord?id=CVE-2018-17142 Référence CVE CVE-2018-17143 https://www.cve.org/CVERecord?id=CVE-2018-17143 Référence CVE CVE-2018-17846 https://www.cve.org/CVERecord?id=CVE-2018-17846 Référence CVE CVE-2018-17847 https://www.cve.org/CVERecord?id=CVE-2018-17847 Référence CVE CVE-2018-17848 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2018-011633Kubernetes におけるエラー処理に関する脆弱性

Kubernetes には、エラー処理に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Kubernetes: v1.0.x, v1.1.x, v1.2.x, v1.3.x, v1.4.x, v1.5.x, v1.6.x, v1.7.x, v1.8.x, v1.9.x, unspecified < v1.10.11, unspecified < v1.11.5, unspecified < v1.12.3
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 5 Dec 2018 · Last source change 5 Aug 2024, 12:47 UTC · CWE-388

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2022-0831
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. ENISA EUVD mappingEUVD-2022-0831 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2022-0831"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added mitigation: coalfire.com/Kubernetes-Vulnerability-What-You-Can-Should-Do; added patch: github.com/71411; removed vendor advisory: access.redhat.com/RHSA-2018:3537; removed vendor advisory: access.redhat.com/RHSA-2018:3549; 1 further additions; 7 further removals.
    Before
    vendor advisory: access.redhat.com/RHSA-2018:3537 · vendor advisory: access.redhat.com/RHSA-2018:3549 · vendor advisory: access.redhat.com/RHSA-2018:3551 · 6 more references
    After
    mitigation: coalfire.com/Kubernetes-Vulnerability-What-You-Can-Should-Do · patch: github.com/71411 · remediation: github.com/71411
    github.com ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    v1.0.x; v1.1.x; v1.2.x; v1.3.x; v1.4.x; v1.5.x; v1.6.x; v1.7.x · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    v1.0.x; v1.1.x; v1.2.x; v1.3.x; v1.4.x; v1.5.x; v1.6.x; v1.7.x · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  4. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    github.com ↗
  5. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-0831↗Mitigation reference↗Patch or update reference↗CVE authority or vendor reference↗Public exploit reference↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2018-1002105 · cve.blacktree.nl