Supportutils up to 3.1-5.7.0 RPM Verification command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Supportutils up to 3.1-5.7.0. It has been classified as critical. The impacted element is an unknown function of the component RPM Verification. Performing a manipulation results in command injection. This vulnerability is known as CVE-2018-19639. Attacking locally is a requirement. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Supportutils up to 3.1-5.7.0. It has been classified as critical. This affects an unknown code block of the component RPM Verification. The manipulation with an unknown input leads to a command injection vulnerability. CWE is classifying the issue as CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
If supportutils before version 3.1-5.7.1 is run with -v to perform rpm verification and the attacker manages to manipulate the rpm listing (e.g. with CVE-2018-19638) he can execute arbitrary commands as root.
The bug was discovered 03/15/2019. The weakness was published 03/05/2019 as Bug 1118462 as confirmed bug report (Bugzilla). The advisory is shared at bugzilla.suse.com. This vulnerability is uniquely identified as CVE-2018-19639 since 11/28/2018. An attack has to be approached locally. The requirement for exploitation is a authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1202 for this issue.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 172133 (OpenSUSE Security Update for supportutils (openSUSE-SU-2019:0293-1)).
Upgrading to version 3.1-5.7.1 eliminates this vulnerability.
Similar entries are available at VDB-131323, VDB-131324 and VDB-131326. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 6.7
CNA Vector (SUSE): 🔍
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: Command injectionCWE: CWE-77 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Supportutils 3.1-5.7.1
Timeline
11/28/2018 🔍03/05/2019 🔍
03/06/2019 🔍
03/15/2019 🔍
07/26/2023 🔍
Sources
Advisory: Bug 1118462Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-19639 (🔍)
GCVE (CVE): GCVE-0-2018-19639
GCVE (VulDB): GCVE-100-131325
See also: 🔍
Entry
Created: 03/06/2019 07:19Updated: 07/26/2023 13:45
Changes: 03/06/2019 07:19 (61), 05/13/2020 17:10 (2), 07/26/2023 13:45 (14)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.