# CVE-2023-5157: Mariadb: node crashes with transport endpoint is not connected mysqld got signal 6

> A malicious remote client can cause a denial of service in MariaDB by triggering a crash via port scans on specific ports.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 26 Sep 2023
- **Updated:** 28 Apr 2026
- **Also known as:** BIT-mariadb-2023-5157, BIT-mariadb-min-2023-5157, BIT-mysql-client-2023-5157, DEBIAN-CVE-2023-5157, GHSA-6589-j38p-mm8c, OESA-2023-1750, UBUNTU-CVE-2023-5157

## What is CVE-2023-5157?

CVE-2023-5157 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 26 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in MariaDB. An OpenVAS port scan on ports 3306 and 4567 allows a malicious remote client to cause a denial of service.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2023-5157?

3 open source packages ship an affected version, including mariadb, mariadb-min and mysql-client. It affects 12 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mariadb` | Bitnami | All versions | 10.3.36, 10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4 |
| `mariadb-min` | Bitnami | All versions | 10.3.36, 10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4 |
| `mysql-client` | Bitnami | All versions | 10.3.36, 10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4 |

Products: Fedoraproject Fedora, Mariadb Mariadb, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux for Arm 64, Redhat Enterprise Linux for Arm 64 Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Little Endian, Redhat Enterprise Linux for Power Little Endian Eus, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus.

## How do I fix CVE-2023-5157?

Upgrade mariadb to a fixed version for your release line: 10.3.36, 10.4.26, 10.5.17 or 10.6.9.

## Is CVE-2023-5157 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5157 and fix it if it is affected.

What it is: CVE-2023-5157 is a high-severity denial of service vulnerability in Fedoraproject Fedora, published on 26 Sep 2023. 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-2023-5157 in the wild and no public exploit code.

Affected packages and fixed versions:
- mariadb (Bitnami): affected all versions; fixed in 10.3.36, 10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4
- mariadb-min (Bitnami): affected all versions; fixed in 10.3.36, 10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4
- mysql-client (Bitnami): affected all versions; fixed in 10.3.36, 10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4

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

## Sources

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

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