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

> Remote attackers can cause a denial of service via memory consumption in the Sophos UTM kernel TCP stack.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vvm2-f57h-2f5r

## What is CVE-2014-2537?

CVE-2014-2537 is a high-severity denial of service vulnerability in n/a, published on 18 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Memory leak in the TCP stack in the kernel in Sophos UTM before 9.109 allows remote attackers to cause a denial of service (memory consumption) via unspecified vectors.

Weakness: CWE-399

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

It affects 2 products.


Products: Sophos Unified Threat Management, Sophos Unified Threat Management Software.

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

No fix has been published for CVE-2014-2537 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-2537 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-25223](https://insights.sbomify.com/CVE-2020-25223/): Sophos SG UTM Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2022-0386](https://insights.sbomify.com/CVE-2022-0386/): SQL injection in Sophos UTM (high 8.8)
- [CVE-2021-25273](https://insights.sbomify.com/CVE-2021-25273/): Cross-site scripting in Sophos UTM (medium 4.8)
- [CVE-2022-0652](https://insights.sbomify.com/CVE-2022-0652/): Information disclosure in Sophos UTM (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2537 is a high-severity denial of service vulnerability in n/a, published on 18 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-2537 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-2537/ (Markdown: https://insights.sbomify.com/CVE-2014-2537/index.md)
```

## Sources

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

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