From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] mariadb: security bump version to 10.3.11
Date: Sun, 30 Dec 2018 16:37:28 +0100 [thread overview]
Message-ID: <20181230163728.525f71c2@windsurf> (raw)
In-Reply-To: <20181229011219.851-1-bluemrp9@gmail.com>
Hello,
On Fri, 28 Dec 2018 17:12:19 -0800, Ryan Coe wrote:
> Remove 0002-cmake-fix-ucontext-dection.path as it is now upstream.
>
> Hash updated for README.md because upstream changed bug report links.
>
> Release notes: https://mariadb.com/kb/en/mariadb-10311-release-notes/
> Changelog: https://mariadb.com/kb/en/mariadb-10311-changelog/
>
> Fixes the following security vulnerabilities:
>
> CVE-2018-3282 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: Server: Storage Engines). Supported versions that are affected
> are 5.5.61 and prior, 5.6.41 and prior, 5.7.23 and prior and 8.0.12 and prior.
> Easily exploitable vulnerability allows high privileged 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.
>
> CVE-2016-9843 - The crc32_big function in crc32.c in zlib 1.2.8 might allow
> context-dependent attackers to have unspecified impact via vectors involving
> big-endian CRC calculation.
>
> CVE-2018-3174 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: Client programs). Supported versions that are affected are
> 5.5.61 and prior, 5.6.41 and prior, 5.7.23 and prior and 8.0.12 and prior.
> Difficult to exploit vulnerability allows high privileged attacker with logon
> to the infrastructure where MySQL Server executes to compromise MySQL Server.
> While the vulnerability is in MySQL Server, attacks may significantly impact
> additional products. Successful attacks of this vulnerability can result in
> unauthorized ability to cause a hang or frequently repeatable crash (complete
> DOS) of MySQL Server.
>
> CVE-2018-3143 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: InnoDB). Supported versions that are affected are 5.6.41 and
> prior, 5.7.23 and prior and 8.0.12 and prior. Easily exploitable vulnerability
> allows low privileged 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.
>
> CVE-2018-3156 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: InnoDB). Supported versions that are affected are 5.6.41 and
> prior, 5.7.23 and prior and 8.0.12 and prior. Easily exploitable vulnerability
> allows low privileged 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.
>
> CVE-2018-3251 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: InnoDB). Supported versions that are affected are 5.6.41 and
> prior, 5.7.23 and prior and 8.0.12 and prior. Easily exploitable vulnerability
> allows low privileged 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.
>
> CVE-2018-3185 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: InnoDB). Supported versions that are affected are 5.7.23 and
> prior and 8.0.12 and prior. Easily exploitable vulnerability allows high
> privileged 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 as well as unauthorized update, insert or delete access
> to some of MySQL Server accessible data. CVSS 3.0 Base Score 5.5 (Integrity
> and Availability impacts).
>
> CVE-2018-3277 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: InnoDB). Supported versions that are affected are 5.7.23 and
> prior and 8.0.12 and prior. Easily exploitable vulnerability allows high
> privileged 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.
>
> CVE-2018-3162 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: InnoDB). Supported versions that are affected are 5.7.23 and
> prior and 8.0.12 and prior. Easily exploitable vulnerability allows high
> privileged 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.
>
> CVE-2018-3173 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: InnoDB). Supported versions that are affected are 5.7.23 and
> prior and 8.0.12 and prior. Easily exploitable vulnerability allows high
> privileged 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.
>
> CVE-2018-3200 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: InnoDB). Supported versions that are affected are 5.7.23 and
> prior and 8.0.12 and prior. Easily exploitable vulnerability allows high
> privileged 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.
>
> CVE-2018-3284 - Vulnerability in the MySQL Server component of Oracle MySQL
> (subcomponent: InnoDB). Supported versions that are affected are 5.7.23 and
> prior and 8.0.12 and prior. Difficult to exploit vulnerability allows high
> privileged 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.
>
> Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
> ---
> .../0002-cmake-fix-ucontext-detection.patch | 44 -------------------
> package/mariadb/mariadb.hash | 12 ++---
> package/mariadb/mariadb.mk | 2 +-
> 3 files changed, 7 insertions(+), 51 deletions(-)
> delete mode 100644 package/mariadb/0002-cmake-fix-ucontext-detection.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-30 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 1:12 [Buildroot] [PATCH 1/1] mariadb: security bump version to 10.3.11 Ryan Coe
2018-12-30 15:37 ` Thomas Petazzoni [this message]
2019-01-18 14:58 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181230163728.525f71c2@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox