From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH][zeus 0/7] zeus review
Date: Tue, 17 Mar 2020 00:30:58 +0800 [thread overview]
Message-ID: <cover.1584375668.git.anuj.mittal@intel.com> (raw)
This series includes some CVE fixes for zeus. Please review.
Thanks,
Anuj
The following changes since commit d8cfc309f9dd0dc8904ab18e5898770502ee2540:
cve-check: fix ValueError (2020-03-15 13:33:19 -0700)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib anujm/zeus
Adrian Bunk (1):
python3: Upgrade 3.7.6 -> 3.7.7
Anuj Mittal (1):
bluez: fix CVE-2020-0556
Lee Chee Yang (2):
qemu: fix CVE-2019-20382
libpcre2: fix CVE-2019-20454
Ross Burton (1):
sqlite: fix numerous CVEs
Stefan Ghinea (1):
aspell: CVE-2019-20433
Wenlin Kang (1):
libarchive: Fix CVE-2020-9308
meta/recipes-connectivity/bluez5/bluez5.inc | 2 +
.../bluez5/bluez5/CVE-2020-0556-1.patch | 35 +
.../bluez5/bluez5/CVE-2020-0556-2.patch | 143 +++
.../{python3_3.7.6.bb => python3_3.7.7.bb} | 6 +-
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2019-20382.patch | 1018 +++++++++++++++++
...ct-files-that-declare-invalid-header.patch | 124 ++
.../libarchive/libarchive_3.4.0.bb | 1 +
.../aspell/aspell/CVE-2019-20433-0001.patch | 999 ++++++++++++++++
.../aspell/aspell/CVE-2019-20433-0002.patch | 68 ++
meta/recipes-support/aspell/aspell_0.60.7.bb | 2 +
.../libpcre/libpcre2/CVE-2019-20454.patch | 19 +
.../recipes-support/libpcre/libpcre2_10.33.bb | 1 +
.../sqlite/sqlite3/CVE-2019-19244.patch | 33 +
.../sqlite/sqlite3/CVE-2019-19923.patch | 50 +
.../sqlite/sqlite3/CVE-2019-19924.patch | 65 ++
.../sqlite/sqlite3/CVE-2019-19925.patch | 33 +
.../sqlite/sqlite3/CVE-2019-19926.patch | 31 +
.../sqlite/sqlite3/CVE-2019-19959.patch | 46 +
.../sqlite/sqlite3/CVE-2019-20218.patch | 31 +
meta/recipes-support/sqlite/sqlite3_3.29.0.bb | 10 +-
21 files changed, 2714 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-connectivity/bluez5/bluez5/CVE-2020-0556-1.patch
create mode 100644 meta/recipes-connectivity/bluez5/bluez5/CVE-2020-0556-2.patch
rename meta/recipes-devtools/python/{python3_3.7.6.bb => python3_3.7.7.bb} (98%)
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2019-20382.patch
create mode 100644 meta/recipes-extended/libarchive/libarchive/0001-RAR5-reader-reject-files-that-declare-invalid-header.patch
create mode 100644 meta/recipes-support/aspell/aspell/CVE-2019-20433-0001.patch
create mode 100644 meta/recipes-support/aspell/aspell/CVE-2019-20433-0002.patch
create mode 100644 meta/recipes-support/libpcre/libpcre2/CVE-2019-20454.patch
create mode 100644 meta/recipes-support/sqlite/sqlite3/CVE-2019-19244.patch
create mode 100644 meta/recipes-support/sqlite/sqlite3/CVE-2019-19923.patch
create mode 100644 meta/recipes-support/sqlite/sqlite3/CVE-2019-19924.patch
create mode 100644 meta/recipes-support/sqlite/sqlite3/CVE-2019-19925.patch
create mode 100644 meta/recipes-support/sqlite/sqlite3/CVE-2019-19926.patch
create mode 100644 meta/recipes-support/sqlite/sqlite3/CVE-2019-19959.patch
create mode 100644 meta/recipes-support/sqlite/sqlite3/CVE-2019-20218.patch
--
2.24.1
next reply other threads:[~2020-03-16 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 16:30 Anuj Mittal [this message]
2020-03-16 16:30 ` [PATCH][zeus 1/7] qemu: fix CVE-2019-20382 Anuj Mittal
2020-03-16 16:31 ` [PATCH][zeus 2/7] libpcre2: fix CVE-2019-20454 Anuj Mittal
2020-03-16 16:31 ` [PATCH][zeus 3/7] sqlite: fix numerous CVEs Anuj Mittal
2020-03-16 16:31 ` [PATCH][zeus 4/7] aspell: CVE-2019-20433 Anuj Mittal
2020-03-16 16:31 ` [PATCH][zeus 5/7] python3: Upgrade 3.7.6 -> 3.7.7 Anuj Mittal
2020-03-16 16:31 ` [PATCH][zeus 6/7] libarchive: Fix CVE-2020-9308 Anuj Mittal
2020-03-16 16:31 ` [PATCH][zeus 7/7] bluez: fix CVE-2020-0556 Anuj Mittal
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=cover.1584375668.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.