All of lore.kernel.org
 help / color / mirror / Atom feed
From: leonardo.sandoval.gonzalez@linux.intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Fixes rpm: CVE-2014-8118 & CVE-2013-6435
Date: Thu, 11 Jun 2015 07:45:45 +0000	[thread overview]
Message-ID: <cover.1434008015.git.leonardo.sandoval.gonzalez@linux.intel.com> (raw)

From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>

Backport fixes for rpm: CVE-2014-8118 & CVE-2013-6435

These two patches only apply on RPM 4.11.2 (already present on RPM 5.4.*). 

https://bugzilla.yoctoproject.org/show_bug.cgi?id=7181

The following changes since commit 062678c4ab88fa94ed38efa6520c3b4e2d88ca73:

  sysvinit: Only enable recipe in builds where its applicable (2015-06-10 12:03:19 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib lsandov1/rpm-vulnerabilities
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=lsandov1/rpm-vulnerabilities

Leonardo Sandoval (2):
  rpm: Fix CVE-2014-8118
  rpm: Fix CVE-2013-6435

 .../rpm/rpm/rpm-CVE-2013-6435.patch                | 109 +++++++++++++++++++++
 .../rpm/rpm/rpm-CVE-2014-8118.patch                |  43 ++++++++
 meta/recipes-devtools/rpm/rpm_4.11.2.bb            |   2 +
 3 files changed, 154 insertions(+)
 create mode 100644 meta/recipes-devtools/rpm/rpm/rpm-CVE-2013-6435.patch
 create mode 100644 meta/recipes-devtools/rpm/rpm/rpm-CVE-2014-8118.patch

-- 
1.8.4.5



             reply	other threads:[~2015-06-11 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  7:45 leonardo.sandoval.gonzalez [this message]
2015-06-11  7:45 ` [PATCH 1/2] rpm: Fix CVE-2014-8118 leonardo.sandoval.gonzalez
2015-06-11  7:45 ` [PATCH 2/2] rpm: Fix CVE-2013-6435 leonardo.sandoval.gonzalez

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.1434008015.git.leonardo.sandoval.gonzalez@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.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.