Bug 1443360 (CVE-2017-3329) - CVE-2017-3329 mysql: Server: Thread Pooling unspecified vulnerability (CPU Apr 2017)
Summary: CVE-2017-3329 mysql: Server: Thread Pooling unspecified vulnerability (CPU Ap...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2017-3329
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1443389
TreeView+ depends on / blocked
 
Reported: 2017-04-19 07:18 UTC by Adam Mariš
Modified: 2021-02-17 02:17 UTC (History)
27 users (show)

Fixed In Version: mysql 5.5.55, mysql 5.6.36, mysql 5.7.18
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-20 14:16:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Adam Mariš 2017-04-19 07:18:18 UTC
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Thread Pooling). Supported versions that are affected are 5.5.54 and earlier, 5.6.35 and earlier and 5.7.17 and earlier. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. 

External References:

http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html#AppendixMSQL

Comment 1 Adam Mariš 2017-04-19 08:12:53 UTC
Created mariadb tracking bugs for this issue:

Affects: fedora-all [bug 1443408]

Comment 2 Adam Mariš 2017-04-19 08:13:08 UTC
Created community-mysql tracking bugs for this issue:

Affects: fedora-all [bug 1443407]

Comment 3 Tomas Hoger 2017-04-20 14:16:38 UTC
MySQL Enterprise Thread Pool is a feature of the MySQL Enterprise Edition, so this CVE is not applicable to the community MySQL version or MariaDB.

https://dev.mysql.com/doc/refman/5.7/en/mysql-enterprise-thread-pool.html

This CVE is most likely related to this entry in the MySQL release notes:

  Thread Pool Notes

  To improve thread_pool plugin performance, connection authentication and
  initialization have been moved from the acceptor thread to the thread pool
  worker threads that handle client connections. This enables the acceptor
  thread to handle new connections at a higher rate with reduced latency. The
  INFORMATION_SCHEMA TP_THREAD_GROUP_STATE table now contains a
  CONNECT_THREAD_COUNT column that indicates the number of threads that are
  processing or waiting to process connection initialization and
  authentication. There can be a maximum of four connection threads per
  thread group; these threads expire after a period of inactivity.
  (Bug #17159742)

https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-18.html#mysqld-5-7-18-thread-pool
https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-36.html#mysqld-5-6-36-thread-pool
https://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-55.html#mysqld-5-5-55-thread-pool

This change apparently aims to prevent exhausting all threads by an unauthenticated connections.


Note You need to log in before you can comment on or make changes to this bug.