Is CVE-2017-3265 exploited in the wild?

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

How severe is CVE-2017-3265?

Medium severity, with a CVSS score of 5.6, 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-3265?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2017-3265 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2017-3265?

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-3265: Oracle MySQL and MariaDB privilege escalation in Server Packaging

CVE-2017-3265 · Severity: medium · CVSS 5.6 · Published 2017-01-27

A vulnerability in the MySQL and MariaDB database server packaging and initialization scripts could allow a highly privileged local user to compromise the database. If exploited, an attacker could gain unauthorized access to all database data or cause the server to crash, leading to a service outage. This attack is difficult to perform as it requires specific local access and interaction from another user.

Technologies: Oracle MySQL Server. Vendors: Oracle.

Quick answers

Is CVE-2017-3265 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-3265 being exploited in the wild.
How severe is CVE-2017-3265?: Medium severity, with a CVSS score of 5.6, 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-3265?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2017-3265 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2017-3265?: 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

The vulnerability exists within the MySQL/MariaDB init scripts and packaging subcomponent, specifically related to how the database data directory is initialized and how permissions are set on error log files. A local attacker with high privileges (such as the 'mysql' operating system user) can exploit these flaws to escalate privileges to root or gain unauthorized access to all MySQL-accessible data. The attack is characterized by high complexity, requiring local infrastructure access and human interaction from a person other than the attacker. Impact includes potential for a complete denial-of-service (DOS) via repeatable crashes and unauthorized confidentiality loss. Patches are available in MySQL 5.5.54, 5.6.35, 5.7.17 and MariaDB 10.0.29.

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 up to 5.5.54, 10.0.0 up to 10.0.29, 10.1.0 up to 10.1.21

Timeline

2017-01-19: advisory: Debian released DSA-3767-1 for mysql-5.5
2017-01-27: disclosed: NVD publication date

References

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