# CVE-2014-3525: Other in n/a

> Unspecified vulnerability in Apache Traffic Server potentially affecting health checks, requiring an upgrade to mitigate unknown risks.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 22 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3525, GHSA-8h6h-w398-77v5

## What is CVE-2014-3525?

CVE-2014-3525 is a critical vulnerability in Apache Traffic Server, published on 22 Aug 2014. It can be exploited over the network.

### Official description

Unspecified vulnerability in Apache Traffic Server 3.x through 3.2.5, 4.x before 4.2.1.1, and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

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

It affects 1 product.


Products: Apache Traffic Server.

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

Upgrade to a fixed version.

## Is CVE-2014-3525 being exploited?

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

## Other vulnerabilities in Apache Traffic Server

- [CVE-2021-43082](https://insights.sbomify.com/CVE-2021-43082/): heap-buffer-overflow with stats-over-http plugin (critical 9.8)
- [CVE-2021-35474](https://insights.sbomify.com/CVE-2021-35474/): Dynamic stack buffer overflow in cachekey plugin (critical 9.8)
- [CVE-2019-17559](https://insights.sbomify.com/CVE-2019-17559/): Other in Apache Traffic Server (critical 9.8)
- [CVE-2019-17565](https://insights.sbomify.com/CVE-2019-17565/): Other in Apache Traffic Server (critical 9.8)
- [CVE-2020-1944](https://insights.sbomify.com/CVE-2020-1944/): Other in Apache Traffic Server (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3525 is a critical vulnerability in Apache Traffic Server, published on 22 Aug 2014. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2014-3525 in the wild and no public exploit code.

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

## Sources

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

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