Home
» Security vulnerabilities
» CVE-2018-1002104
Versions < 1.5 of the Kubernetes ingress default backend, which handles invalid ingress traffic, exposed prometheus metrics publicly.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2018-1002104
Conclusion & alert: CVE-2018-1002104 is rated Moderate Risk (43.1/100) : CVSS Medium severity, with medium exploitation likelihood (EPSS 0.44%).Mandatory action: Review affected assets and schedule remediation.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2018-1002104
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2025-11-21
0.27%
0.44%
+0.17%
2
2025-11-18
0.44%
0.27%
-0.17%
3
2025-04-29
—
0.44%
—
Full EPSS history
(9 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2018-1002104
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
5.3
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
3.9
1.4
[email protected]
5.3
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
3.9
1.4
[email protected]
5.0
2.0
MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
10.0
2.9
[email protected]
Weakness enumeration for CVE-2018-1002104
GitHub Security Advisory for CVE-2018-1002104
GHSA-p3x5-5xpx-9phm · Severity: medium · Ecosystem: go
— Kubernetes ingress exposes sensitive information
OS Trackers for CVE-2018-1002104
Affected software / configurations for CVE-2018-1002104
References for CVE-2018-1002104
cvelogic
Threat Intelligence