# CVE-2014-0180: Denial of service in n/a

> Remote attackers can cause a denial of service in Red Hat CloudForms via an infinite loop in the wait_for_task function.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p9jr-2p44-p728

## What is CVE-2014-0180?

CVE-2014-0180 is a medium-severity denial of service vulnerability in n/a, published on 7 Jul 2014. It can be exploited over the network, with no action from the victim.

### Official description

The wait_for_task function in app/controllers/application_controller.rb in Red Hat CloudForms 3.0 Management Engine (CFME) before 5.2.4.2 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via unspecified vectors.

Weakness: CWE-399

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

It affects 1 product.


Products: Redhat Cloudforms 3.0 Management Engine.

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

Upgrade to a fixed version.

## Is CVE-2014-0180 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-3486](https://insights.sbomify.com/CVE-2014-3486/): Path traversal in n/a (medium 6.9)
- [CVE-2014-7813](https://insights.sbomify.com/CVE-2014-7813/): Denial of service in n/a (medium 6.5)
- [CVE-2014-0137](https://insights.sbomify.com/CVE-2014-0137/): SQL injection in n/a (medium 6.5)
- [CVE-2014-0136](https://insights.sbomify.com/CVE-2014-0136/): Other in n/a (medium 5.0)
- [CVE-2014-0184](https://insights.sbomify.com/CVE-2014-0184/): Information disclosure in n/a (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0180 is a medium-severity denial of service vulnerability in n/a, published on 7 Jul 2014. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0180 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-0180/ (Markdown: https://insights.sbomify.com/CVE-2014-0180/index.md)
```

## Sources

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

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