# CVE-2014-0091: Denial of service in Foreman

> Attackers can cause partial denial of service in Foreman through improper input validation, affecting IT infrastructure management availability.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Dec 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m3r2-wj3v-57ch

## What is CVE-2014-0091?

CVE-2014-0091 is a medium-severity denial of service vulnerability in Theforeman Foreman, published on 11 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Foreman has improper input validation which could lead to partial Denial of Service

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Theforeman Foreman.

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

Apply the vendor's patch.

## Is CVE-2014-0091 being exploited?

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

## Other vulnerabilities in Theforeman Foreman

- [CVE-2018-14643](https://insights.sbomify.com/CVE-2018-14643/): smart_proxy_dynflow gem authentication bypass in Foreman remote execution feature (critical 9.8)
- [CVE-2017-7505](https://insights.sbomify.com/CVE-2017-7505/): Missing authorization in foreman (high 8.8)
- [CVE-2016-4475](https://insights.sbomify.com/CVE-2016-4475/): Missing authorization in n/a (high 8.8)
- [CVE-2016-3728](https://insights.sbomify.com/CVE-2016-3728/): Code injection in n/a (high 8.8)
- [CVE-2015-5246](https://insights.sbomify.com/CVE-2015-5246/): Auth bypass in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0091 is a medium-severity denial of service vulnerability in Theforeman Foreman, published on 11 Dec 2019. 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-0091 in the wild and no public exploit code.

Affected product: Theforeman Foreman. 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-0091/ (Markdown: https://insights.sbomify.com/CVE-2014-0091/index.md)
```

## Sources

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

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