# CVE-2015-1027: Information disclosure in n/a

> Attackers can perform man-in-the-middle attacks to disclose MySQL running configuration information via vulnerable version checking subroutines.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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-2015-1027, GHSA-6q75-456q-rjf2

## What is CVE-2015-1027?

CVE-2015-1027 is a medium-severity 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 version checking subroutine in percona-toolkit before 2.2.13 and xtrabackup before 2.2.9 was vulnerable to silent HTTP downgrade attacks and Man In The Middle attacks in which the server response could be modified to allow the attacker to respond with modified command payload and have the client return additional running configuration information leading to an information disclosure of running configuration of MySQL.

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

## Which versions are affected by CVE-2015-1027?

It affects 2 products.


Products: Percona Toolkit, Percona Xtrabackup.

## How do I fix CVE-2015-1027?

Upgrade to a fixed version.

## Is CVE-2015-1027 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2029](https://insights.sbomify.com/CVE-2014-2029/): Server-side request forgery in n/a (high 8.1)
- [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-2015-1027 and fix it if it is affected.

What it is: CVE-2015-1027 is a medium-severity 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-2015-1027 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-2015-1027/ (Markdown: https://insights.sbomify.com/CVE-2015-1027/index.md)
```

## Sources

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

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