Is CVE-2017-3258 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2017-3258 being exploited in the wild.

How severe is CVE-2017-3258?

Medium severity, with a CVSS score of 6.5, published 27 January 2017.

Which products and versions are affected?

Oracle MySQL Server 5.5.53 and earlier, 5.6.34 and earlier, 5.7.16 and earlier.

Is there a fix for CVE-2017-3258?

A patch was published on 2017-01-19: Debian released fixed mysql-5.5 packages Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2017-3258 attacked?

It is attacked over the network, in an operating system.

Am I affected by CVE-2017-3258?

Check whether you run Oracle MySQL Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2017-3258: Oracle MySQL and MariaDB denial of service in DDL subcomponent

CVE-2017-3258 · Severity: medium · CVSS 6.5 · Published 2017-01-27

A vulnerability in the MySQL and MariaDB database servers could allow a user with low-level access to crash the database service remotely. This component is responsible for managing data structures, and an exploit would result in a complete denial of service, making the database and any dependent applications unavailable. Organizations relying on these databases for operations or customer-facing services may experience significant downtime until the service is manually restarted.

Technologies: Oracle MySQL Server. Vendors: Oracle.

Quick answers

Is CVE-2017-3258 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3258 being exploited in the wild.
How severe is CVE-2017-3258?: Medium severity, with a CVSS score of 6.5, published 27 January 2017.
Which products and versions are affected?: Oracle MySQL Server 5.5.53 and earlier, 5.6.34 and earlier, 5.7.16 and earlier.
Is there a fix for CVE-2017-3258?: A patch was published on 2017-01-19: Debian released fixed mysql-5.5 packages Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-3258 attacked?: It is attacked over the network, in an operating system.
Am I affected by CVE-2017-3258?: Check whether you run Oracle MySQL Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability exists in the Server: DDL (Data Definition Language) subcomponent of Oracle MySQL and MariaDB. The flaw is caused by improper input validation during DDL operations. An attacker with low-privileged network access can exploit this vulnerability via multiple protocols to trigger a hang or a frequently repeatable crash (Denial of Service). The issue affects MySQL versions up to 5.5.53, 5.6.34, and 5.7.16, as well as several MariaDB versions. Patches are available in MySQL 5.5.54, 5.6.35, 5.7.17, and MariaDB 10.0.29 / 10.1.21.

Affected products

Oracle MySQL Server 5.5.53 and earlier, 5.6.34 and earlier, 5.7.16 and earlier
MariaDB Foundation MariaDB 5.5.0 to 5.5.53, 10.0.0 to 10.0.28, 10.1.0 to 10.1.20

Timeline

2017-01-17: advisory: Oracle Critical Patch Update (CPU) published
2017-01-19: patched: Debian released fixed mysql-5.5 packages
2017-01-27: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.