Kubernetes up to 1.4 Ingress Default Backend insertion of sensitive information into debugging code
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Kubernetes up to 1.4 and classified as problematic. This affects an unknown part of the component Ingress Default Backend. The manipulation results in insertion of sensitive information into debugging code. This vulnerability is identified as CVE-2018-1002104. The attack can be executed remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Kubernetes up to 1.4 (Virtualization Software). Affected is an unknown code of the component Ingress Default Backend. The manipulation with an unknown input leads to a insertion of sensitive information into debugging code vulnerability. CWE is classifying the issue as CWE-215. The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production. This is going to have an impact on confidentiality. CVE summarizes:
Versions < 1.5 of the Kubernetes ingress default backend, which handles invalid ingress traffic, exposed prometheus metrics publicly.
The weakness was released 01/14/2020 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2018-1002104 since 12/05/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
Upgrading to version 1.5 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (Kubernetes): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Insertion of sensitive information into debugging codeCWE: CWE-215 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kubernetes 1.5
Patch: github.com
Timeline
12/05/2018 🔍01/14/2020 🔍
01/15/2020 🔍
03/21/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-1002104 (🔍)
GCVE (CVE): GCVE-0-2018-1002104
GCVE (VulDB): GCVE-100-148656
Entry
Created: 01/15/2020 08:32Updated: 03/21/2024 09:38
Changes: 01/15/2020 08:32 (38), 01/15/2020 08:37 (12), 03/21/2024 09:34 (17), 03/21/2024 09:38 (18)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.