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

> Remote attackers can cause denial of service in OpenStack Dashboard by flooding the login page when using specific session engines.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-8124, GHSA-q878-vxpg-6qx6, RHSA-2015:0839, RHSA-2015:0845, UBUNTU-CVE-2014-8124

## What is CVE-2014-8124?

CVE-2014-8124 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 12 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenStack Dashboard (Horizon) before 2014.1.3 and 2014.2.x before 2014.2.1 does not properly handle session records when using a db or memcached session engine, which allows remote attackers to cause a denial of service via a large number of requests to the login page.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-dashboard` | Red Hat:openstack:5::el6 | All versions | 0:2014.1.4-1.el6ost |
| `openstack-dashboard-theme` | Red Hat:openstack:5::el6 | All versions | 0:2014.1.4-1.el6ost |
| `python-django-horizon` | Red Hat:openstack:5::el6 | All versions | 0:2014.1.4-1.el6ost |
| `python-django-horizon-doc` | Red Hat:openstack:5::el6 | All versions | 0:2014.1.4-1.el6ost |
| `python-django-openstack-auth` | Red Hat:openstack:5::el6 | All versions | 0:1.1.5-4.el6ost |
| `openstack-dashboard` | Red Hat:openstack:5::el7 | All versions | 0:2014.1.4-1.el7ost |
| `openstack-dashboard-theme` | Red Hat:openstack:5::el7 | All versions | 0:2014.1.4-1.el7ost |
| `python-django-horizon` | Red Hat:openstack:5::el7 | All versions | 0:2014.1.4-1.el7ost |
| `python-django-horizon-doc` | Red Hat:openstack:5::el7 | All versions | 0:2014.1.4-1.el7ost |
| `python-django-openstack-auth` | Red Hat:openstack:5::el7 | All versions | 0:1.1.5-4.el7ost |

Products: Fedoraproject Fedora, Openstack Horizon, Opensuse Opensuse, Oracle Solaris.

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

Upgrade to a fixed version.

## Is CVE-2014-8124 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8124 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 12 Dec 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-8124 in the wild and no public exploit code.

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

## Sources

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

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