# CVE-2014-0022: Security feature bypass in n/a

> Remote attackers can bypass RPM package signing restrictions in yum-cron by installing unsigned packages due to improper return value checking.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f9cg-v6pq-9w58, RHSA-2014:1004, UBUNTU-CVE-2014-0022

## What is CVE-2014-0022?

CVE-2014-0022 is a medium-severity vulnerability in n/a, published on 26 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-0022?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yum-updatesd` | Red Hat:enterprise_linux:5::client | All versions | 1:0.9-6.el5_10 |
| `yum-updatesd` | Red Hat:enterprise_linux:5::server | All versions | 1:0.9-6.el5_10 |

Products: Baseurl Yum.

## How do I fix CVE-2014-0022?

Apply the vendor's patch.

## Is CVE-2014-0022 being exploited?

There is no known exploitation of CVE-2014-0022 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-1910](https://insights.sbomify.com/CVE-2013-1910/): Denial of service in yum (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0022 and fix it if it is affected.

What it is: CVE-2014-0022 is a medium-severity vulnerability in n/a, published on 26 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0022 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-0022/ (Markdown: https://insights.sbomify.com/CVE-2014-0022/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0022
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0022
- OSV: https://osv.dev/vulnerability/CVE-2014-0022

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-0022/
Summaries are generated and may contain mistakes; the official description above is the record.