# CVE-2017-3590: MySQL Connectors Privilege Escalation


- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Apr 2017
- **Updated:** 7 Oct 2024
- **Also known as:** GHSA-2cf3-g243-hhfx, PYSEC-2026-682, UBUNTU-CVE-2017-3590

## What is CVE-2017-3590?

CVE-2017-3590 is a low-severity vulnerability in Oracle Corporation MySQL Connectors, published on 24 Apr 2017. 

### Official description

Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/Python). Supported versions that are affected are 2.1.5 and earlier. Easily "exploitable" vulnerability allows low privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data. CVSS 3.0 Base Score 3.3 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N).

## Which versions are affected by CVE-2017-3590?

3 open source packages ship an affected version, including mysql-connector-python. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mysql-connector-python` | PyPI | All versions to 2.1.5 | None |
| `mysql-connector-python` | PyPI | All versions to 2.1.5 | None |
| `mysql-connector-python` | PyPI | All versions to 2.1.5 | None |

Products: Oracle Connector\/Python.

## How do I fix CVE-2017-3590?

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

## Is CVE-2017-3590 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3590 and fix it if it is affected.

What it is: CVE-2017-3590 is a low-severity vulnerability in Oracle Corporation MySQL Connectors, published on 24 Apr 2017. 
Exploitation: There is no known exploitation of CVE-2017-3590 in the wild and no public exploit code.

Affected packages and fixed versions:
- mysql-connector-python (PyPI): affected all versions up to 2.1.5; no fix listed
- mysql-connector-python (PyPI): affected all versions up to 2.1.5; no fix listed
- mysql-connector-python (PyPI): affected all versions up to 2.1.5; no fix listed

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-2017-3590/ (Markdown: https://insights.sbomify.com/CVE-2017-3590/index.md)
```

## Sources

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

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