CVE-2014-0022
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 · uneditedThe installUpdates function in yum-cron/yum-cron.py in yum 3.4.3 and earlier does not properly check the return value of the sigCheckPkg function, which allows remote attackers to bypass the RMP package signing restriction via an unsigned package.
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 · high confidenceThe yum-cron utility's installUpdates function in yum 3.4.3 and earlier fails to properly check the return value from the sigCheckPkg function, which validates RPM package signatures. This allows unsigned or improperly signed RPM packages to be installed, bypassing the package signing security mechanism intended to verify package integrity and authenticity.
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<= 3.4.3= 3.4.0= 3.4.1= 3.4.2CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify yum-cron is installedRun 'rpm -qa | grep yum-cron' or 'yum list installed yum-cron' to see if the yum-cron package is present on the systemAffected if yum-cron is installed and the system uses automatic updates via yum-cron
-
Check the installed yum versionRun 'yum --version' or 'rpm -qa | grep yum' to determine the exact yum version installedAffected if yum version is 3.4.3 or earlier (3.4.0, 3.4.1, 3.4.2, or any version <= 3.4.3)
-
Confirm yum-cron service is enabledRun 'systemctl is-enabled yum-cron' or 'chkconfig --list yum-cron' to see if the automatic update service is configured to runAffected if yum-cron service is enabled and will automatically install updates
-
Inspect yum-cron configuration for update behaviorCheck /etc/yum/yum-cron.conf or /etc/sysconfig/yum-cron for the 'update_cmd' and 'update_messages' settings to see if it applies updates automaticallyAffected if yum-cron is configured to automatically apply updates (update_cmd is set to 'default' or 'security' with auto-download enabled)
-
Verify GPG signature checking configurationCheck /etc/yum.conf for 'gpgcheck=1' and ensure repo configuration files in /etc/yum.repos.d/ have 'gpgcheck=1' set for each enabled repositoryAffected if gpgcheck is disabled (set to 0) or missing, allowing unsigned packages to be accepted
The system is affected if yum version 3.4.3 or earlier is installed AND yum-cron is enabled to automatically apply updates, because the signature validation bypass could allow unsigned packages to install during automated updates.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate yum-cron to a version that properly validates and enforces the return value of sigCheckPkg, ensuring unsigned packages are rejected. In the interim, disable automatic updates or restrict network access to trusted update sources.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0022 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0022 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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