CVE-2018-1002104

MEDIUMNVD 5.35.3—

5.3

Versions < 1.5 of the Kubernetes ingress default backend, which handles invalid ingress traffic, exposed prometheus metrics publicly.

CVSS v3: 5.3
EG Score: 5.3(medium)
EPSS: 63.1%
KEV: Not listed

Published

January 14, 2020

Last Modified

November 21, 2024

References (2)

jordan@liggitthttps://github.com/kubernetes/ingress-nginx/pull/3125
af854a3a-2127-422b-91ae-364da2661108https://github.com/kubernetes/ingress-nginx/pull/3125

Affected Packages

(1 across 1 ecosystem)

Go(1)

Package	Vulnerable range	Fixed in	Dependents
k8s.io/ingress-nginx	—	1.5	—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 09:16 UTCEG score recompute
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2018-1002104?

CVE-2018-1002104 is a medium vulnerability published on January 14, 2020. Versions < 1.5 of the Kubernetes ingress default backend, which handles invalid ingress traffic, exposed prometheus metrics publicly.

When was CVE-2018-1002104 disclosed?

CVE-2018-1002104 was first published in the National Vulnerability Database on January 14, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2018-1002104 actively exploited?

CVE-2018-1002104 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 63.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2018-1002104?

CVE-2018-1002104 has a CVSS v3 base score of 5.3 (NVD).

How do I remediate CVE-2018-1002104?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-1002104, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-1002104

Explore →

Is Your Infrastructure Affected by CVE-2018-1002104?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs