# CVE-2014-0226: Race condition in n/a

> Remote attackers can cause denial of service or execute arbitrary code via a race condition in the Apache mod_status module.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 20 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-0226, GHSA-9c3m-phm4-whxx, UBUNTU-CVE-2014-0226

## What is CVE-2014-0226?

CVE-2014-0226 is a medium-severity vulnerability in Apache Http Server, published on 20 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Race condition in the mod_status module in the Apache HTTP Server before 2.4.10 allows remote attackers to cause a denial of service (heap-based buffer overflow), or possibly obtain sensitive credential information or execute arbitrary code, via a crafted request that triggers improper scoreboard handling within the status_handler function in modules/generators/mod_status.c and the lua_ap_scoreboard_worker function in modules/lua/lua_request.c.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 6 products.


Products: Apache Http Server, Debian Debian Linux, Oracle Enterprise Manager Ops Center, Oracle Http Server, Oracle Secure Global Desktop, Redhat Jboss Enterprise Application Platform.

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

Upgrade to a fixed version.

## Is CVE-2014-0226 being exploited?

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

Public exploit code:

- Apache 2.4.7 mod_status - Scoreboard Handling Race Condition (exploitdb)
- https://github.com/shreesh1/CVE-2014-0226-poc (github_poc): https://github.com/shreesh1/CVE-2014-0226-poc

## Other vulnerabilities in Apache Http Server

- [CVE-2021-42013](https://insights.sbomify.com/CVE-2021-42013/): Apache HTTP Server Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2024-38475](https://insights.sbomify.com/CVE-2024-38475/): Apache HTTP Server Improper Escaping of Output (critical 9.1, exploited in the wild)
- [CVE-2021-40438](https://insights.sbomify.com/CVE-2021-40438/): Apache HTTP Server-Side Request Forgery (SSRF) (critical 9.0, exploited in the wild)
- [CVE-2019-0211](https://insights.sbomify.com/CVE-2019-0211/): Apache HTTP Server Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2021-41773](https://insights.sbomify.com/CVE-2021-41773/): Apache HTTP Server Path Traversal (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0226 is a medium-severity vulnerability in Apache Http Server, published on 20 Jul 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-0226 in the wild and no public exploit code.

Affected product: Apache Http Server. 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-0226/ (Markdown: https://insights.sbomify.com/CVE-2014-0226/index.md)
```

## Sources

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

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