# CVE-2020-13249: Other in n/a > The MariaDB Connector/C library fails to properly validate OK packet content, potentially leading to undefined behavior or security issues. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something - **Fix available:** Yes - **Published:** 20 May 2020 - **Updated:** 4 Aug 2024 - **Also known as:** ALPINE-CVE-2020-13249, GHSA-44c7-hc99-224f, JLSEC-2026-211, SUSE-SU-2020:1423-1, SUSE-SU-2020:1431-1, UBUNTU-CVE-2020-13249, openSUSE-SU-2020:0738-1, openSUSE-SU-2024:11039-1 ## What is CVE-2020-13249? CVE-2020-13249 is a high-severity vulnerability in Fedoraproject Fedora, published on 20 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description libmariadb/mariadb_lib.c in MariaDB Connector/C before 3.1.8 does not properly validate the content of an OK packet received from a server. NOTE: although mariadb_lib.c was originally based on code shipped for MySQL, this issue does not affect any MySQL components supported by Oracle. ## Which versions are affected by CVE-2020-13249? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mariadb-connector-c` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 3.1.8-3.18.1 | | `mariadb-connector-c` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 3.1.8-3.18.1 | | `mariadb-connector-c` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 3.1.8-3.18.1 | | `mariadb-connector-c` | SUSE:Linux Enterprise Module for Server Applications 15 SP1 | All versions | 3.1.8-3.18.1 | | `mariadb-connector-c` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 3.1.8-2.15.1 | | `mariadb-connector-c` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 3.1.8-2.15.1 | | `mariadb-connector-c` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 3.1.8-3.18.1 | | `mariadb-connector-c` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 3.1.8-2.15.1 | | `mariadb-connector-c` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 3.1.8-2.15.1 | | `mariadb-connector-c` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 3.1.8-3.18.1 | | `mariadb-connector-c` | openSUSE:Leap 15.1 | All versions | 3.1.8-lp151.3.12.1 | Products: Fedoraproject Fedora, Mariadb Connector\/C, Opensuse Leap. ## How do I fix CVE-2020-13249? Upgrade to a fixed version. ## Is CVE-2020-13249 being exploited? There is no known exploitation of CVE-2020-13249 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-2020-13249 and fix it if it is affected. What it is: CVE-2020-13249 is a high-severity vulnerability in Fedoraproject Fedora, published on 20 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2020-13249 in the wild and no public exploit code. Affected product: Fedoraproject Fedora. 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-2020-13249/ (Markdown: https://insights.sbomify.com/CVE-2020-13249/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-13249 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-13249 - OSV: https://osv.dev/vulnerability/CVE-2020-13249 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-13249/ Summaries are generated and may contain mistakes; the official description above is the record.