dbcve.org
Redhat Upgrade ToolApplication · Redhat

CVE-2014-3585

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
redhat-upgrade-tool: Does not check GPG signatures when upgrading versions

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

The redhat-upgrade-tool fails to validate GPG signatures on packages during the upgrade process, allowing untrusted or tampered packages to be installed without verification. This critical flaw enables remote attackers to inject malicious code via man-in-the-middle attacks during system upgrades.

MitigationDisable or avoid using redhat-upgrade-tool until a patch implementing GPG signature verification is available; consider alternative upgrade methods that enforce signature validation.

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
Redhat Upgrade ToolApplication
Affected:all versions
Enterprise LinuxOperating system
Affected:= 6.0= 7.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 redhat-upgrade-tool is installed
    Run `rpm -q redhat-upgrade-tool` or `which redhat-upgrade-tool`
    Affected if The package is installed (all versions are affected)
  2. Verify the installed version
    Run `rpm -q --info redhat-upgrade-tool` to see the version and release number
    Affected if Any version is installed since all versions are affected per the CVE data
  3. Check for upgrade repository configurations
    Look in /etc/yum.repos.d/ or /etc/rhsm/ for repo files related to upgrade (e.g., upgrade repos used by redhat-upgrade-tool)
    Affected if Upgrade repositories are configured and the tool would be used for system upgrades
  4. Check for recent or scheduled upgrade-tool usage
    Review system logs in /var/log/ for yum or redhat-upgrade-tool usage, and check cron jobs for scheduled upgrades using this tool
    Affected if The tool has been or is scheduled to be used for system upgrades
  5. Confirm RHEL version
    Run `cat /etc/redhat-release` to determine if the system is RHEL 6.0 or 7.0
    Affected if The system is RHEL 6.0 or 7.0 and uses redhat-upgrade-tool

A system is affected if redhat-upgrade-tool is installed and configured for use on RHEL 6.0 or 7.0, as the tool fails to validate GPG signatures on packages during upgrades in all versions.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or avoid using redhat-upgrade-tool until a patch implementing GPG signature verification is available; consider alternative upgrade methods that enforce signature validation.

Recommended fix Moderate confidence

Latest available redhat-upgrade-tool package from Red Hat Update Channel (contact Red Hat support for specific version)

  1. Obtain the latest redhat-upgrade-tool package from Red Hat's official update channels (RHN or Satellite)
  2. Ensure GPG keys for the target Red Hat Enterprise Linux version are properly configured and trusted
  3. Run 'redhat-upgrade-tool --help' to verify the tool now includes signature verification options
  4. Before upgrading, verify the tool's version includes the signature verification fix by consulting Red Hat's errata
Caveat Review Red Hat upgrade path documentation to ensure compatibility between source and target versions before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Redhat Upgrade Tool Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3585 — 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-2014-3585 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