# CVE-2017-10379: Missing authorization in n/a

> A low-privileged attacker can exploit a missing authorization check in MySQL Server client programs to access critical data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-hr5m-vvhf-96cx, UBUNTU-CVE-2017-10379

## What is CVE-2017-10379?

CVE-2017-10379 is a medium-severity missing authorization vulnerability in Debian Debian Linux, published on 19 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Client programs). Supported versions that are affected are 5.5.57 and earlier, 5.6.37 and earlier and 5.7.19 and earlier. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all MySQL Server accessible data. CVSS 3.0 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 17 products.


Products: Debian Debian Linux, Mariadb Mariadb, Netapp Active Iq Unified Manager, Netapp Oncommand Balance, Netapp Oncommand Insight, Netapp Oncommand Performance Manager, Netapp Oncommand Unified Manager, Netapp Oncommand Workflow Automation, Netapp Snapcenter, Oracle Mysql, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Redhat Openstack.

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

Apply the vendor's patch.

## Is CVE-2017-10379 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10379 is a medium-severity missing authorization vulnerability in Debian Debian Linux, published on 19 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10379 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2017-10379/ (Markdown: https://insights.sbomify.com/CVE-2017-10379/index.md)
```

## Sources

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

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