dbcve.org
SupportutilsApplication · Opensuse

CVE-2018-19639

HIGH · 7.8 CVSS v3.0 Published 2019-03-05
Fix available
A fix is available. Upgrade to 3.1-5.7.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

When supportutils version prior to 3.1-5.7.1 is run with the -v flag to perform rpm verification, an attacker who has already compromised the rpm listing (e.g., via CVE-2018-19638) can inject and execute arbitrary commands with root privileges.

MitigationUpdate supportutils to version 3.1-5.7.1 or later. Additionally, ensure protection against CVE-2018-19638 to prevent manipulation of rpm listings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SupportutilsApplication
Affected:< 3.1-5.7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if supportutils is installed
    Run 'rpm -q supportutils' or 'which supportutils'
    Affected if supportutils is not installed, then not affected by this CVE
  2. Determine installed supportutils version
    Run 'rpm -q --queryformat '%{VERSION}-%{RELEASE}' supportutils' or 'supportutils --version'
    Affected if version is lower than 3.1-5.7.1 (e.g., 3.1-5.6.0 or earlier)
  3. Check for supportutils execution with -v flag
    Review system logs, audit logs (/var/log/audit/audit.log), or process history for commands like 'supportutils -v' or 'supportutils --verify'
    Affected if supportutils has been run with the -v flag on a system with a vulnerable version (< 3.1-5.7.1)
  4. Check for signs of rpm database manipulation (CVE-2018-19638)
    Run 'rpm -Va' to verify rpm package integrity and look for unexpected modifications to rpm database files in /var/lib/rpm/
    Affected if rpm database has been tampered with, indicating the prerequisite for CVE-2018-19639 exploitation

A system is affected if supportutils version is below 3.1-5.7.1 AND the -v flag has been executed with a compromised rpm database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 3.1-5.7.1 or later
Fixed in 3.1-5.7.1
Interim mitigation

Update supportutils to version 3.1-5.7.1 or later. Additionally, ensure protection against CVE-2018-19638 to prevent manipulation of rpm listings.

Fix this in Supportutils Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-19639 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-19639 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data