# CVE-2014-2029: Server-side request forgery in n/a

> Man-in-the-middle attackers can execute arbitrary code or read sensitive data via insecure HTTP downloads in Percona Toolkit's version check.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-2029, GHSA-8ch9-48h9-cqjf

## What is CVE-2014-2029?

CVE-2014-2029 is a high-severity server-side request forgery vulnerability in n/a, published on 28 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The automatic version check functionality in the tools in Percona Toolkit 2.1 allows man-in-the-middle attackers to obtain sensitive information or execute arbitrary code by leveraging use of HTTP to download configuration information from v.percona.com.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Percona Toolkit.

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

Apply the vendor's patch.

## Is CVE-2014-2029 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-1027](https://insights.sbomify.com/CVE-2015-1027/): Information disclosure in n/a (medium 5.9)
- [CVE-2024-7701](https://insights.sbomify.com/CVE-2024-7701/): Misuse of SHA256 to create an encryption key (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2029 is a high-severity server-side request forgery vulnerability in n/a, published on 28 Sep 2017. 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-2029 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-2029/ (Markdown: https://insights.sbomify.com/CVE-2014-2029/index.md)
```

## Sources

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

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