# CVE-2014-0133: Memory corruption in n/a

> Remote attackers can execute arbitrary code on nginx servers via a crafted SPDY request due to a heap-based buffer overflow.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** 28 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-0133, GHSA-m342-r7h7-vj42, MGASA-2014-0136

## What is CVE-2014-0133?

CVE-2014-0133 is a high-severity memory corruption vulnerability in Opensuse Opensuse, published on 28 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in the SPDY implementation in nginx 1.3.15 before 1.4.7 and 1.5.x before 1.5.12 allows remote attackers to execute arbitrary code via a crafted request.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


Products: F5 Nginx, Opensuse Opensuse.

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

Upgrade to a fixed version.

## Is CVE-2014-0133 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2016-1247](https://insights.sbomify.com/CVE-2016-1247/): Path traversal in n/a (high 7.8)
- [CVE-2021-23017](https://insights.sbomify.com/CVE-2021-23017/): Memory corruption in Nginx Web Server, Nginx Plus (high 7.7)
- [CVE-2014-0088](https://insights.sbomify.com/CVE-2014-0088/): Memory corruption in n/a (high 7.5)
- [CVE-2013-4547](https://insights.sbomify.com/CVE-2013-4547/): Security feature bypass in n/a (high 7.5)
- [CVE-2013-0337](https://insights.sbomify.com/CVE-2013-0337/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0133 is a high-severity memory corruption vulnerability in Opensuse Opensuse, published on 28 Mar 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-0133 in the wild and no public exploit code.

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

## Sources

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

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