Tower up to 3.4.2 on OpenShift/Kubernetes Playbook Job Credentials credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Tower up to 3.4.2 on OpenShift/Kubernetes. It has been classified as problematic. This affects an unknown part of the component Playbook Job Handler. Performing a manipulation results in credentials management (Credentials). This vulnerability is known as CVE-2019-3869. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Tower up to 3.4.2 on OpenShift/Kubernetes. It has been classified as problematic. This affects an unknown code block of the component Playbook Job Handler. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:
When running Tower before 3.4.3 on OpenShift or Kubernetes, application credentials are exposed to playbook job runs via environment variables. A malicious user with the ability to write playbooks could use this to gain administrative privileges.
The bug was discovered 04/03/2019. The weakness was published 03/28/2019 as not defined bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2019-3869 since 01/03/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. The requirement for exploitation is a authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
Upgrading to version 3.4.3 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CNA Base Score: 7.2
CNA Vector (Red Hat, Inc.): 🔍
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
Name: CredentialsClass: Credentials management / Credentials
CWE: CWE-255
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: Tower 3.4.3
Patch: github.com
Timeline
01/03/2019 🔍03/28/2019 🔍
03/29/2019 🔍
04/03/2019 🔍
08/17/2023 🔍
Sources
Advisory: bugzilla.redhat.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-3869 (🔍)
GCVE (CVE): GCVE-0-2019-3869
GCVE (VulDB): GCVE-100-132585
Entry
Created: 03/29/2019 07:07Updated: 08/17/2023 14:49
Changes: 03/29/2019 07:07 (59), 05/22/2020 16:57 (2), 08/17/2023 14:47 (4), 08/17/2023 14:49 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.