From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: rongqing.li@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] dpkg: upgrade to 1.17.25
Date: Mon, 04 May 2015 10:14:29 -0500 [thread overview]
Message-ID: <55478CD5.5060303@linux.intel.com> (raw)
In-Reply-To: <1430294978-24756-1-git-send-email-rongqing.li@windriver.com>
Hi,
On 29/04/15 03:09, rongqing.li@windriver.com wrote:
> From: Roy Li <rongqing.li@windriver.com>
>
> upgrade to fix two CVE defects: CVE-2014-8625 and CVE-2015-0840
>
> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-8625
>
> Multiple format string vulnerabilities in the parse_error_msg
> function in parsehelp.c in dpkg before 1.17.22 allow remote attackers
> to cause a denial of service (crash) and possibly execute arbitrary
> code via format string specifiers in the (1) package or (2)
> architecture name.
>
> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-0840
>
> The dpkg-source command in Debian dpkg before 1.16.16 and 1.17.x before
> 1.17.25 allows remote attackers to bypass signature verification
> via a crafted Debian source control file (.dsc).
>
> Signed-off-by: Roy Li <rongqing.li@windriver.com>
> ---
> meta/recipes-devtools/dpkg/{dpkg_1.17.21.bb => dpkg_1.17.25.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-devtools/dpkg/{dpkg_1.17.21.bb => dpkg_1.17.25.bb} (81%)
>
> diff --git a/meta/recipes-devtools/dpkg/dpkg_1.17.21.bb b/meta/recipes-devtools/dpkg/dpkg_1.17.25.bb
> similarity index 81%
> rename from meta/recipes-devtools/dpkg/dpkg_1.17.21.bb
> rename to meta/recipes-devtools/dpkg/dpkg_1.17.25.bb
> index ebb8671..74b1dd0 100644
> --- a/meta/recipes-devtools/dpkg/dpkg_1.17.21.bb
> +++ b/meta/recipes-devtools/dpkg/dpkg_1.17.25.bb
> @@ -15,6 +15,6 @@ SRC_URI += "file://noman.patch \
> file://add_armeb_triplet_entry.patch \
> "
>
> -SRC_URI[md5sum] = "765a96fd0180196613bbfa3c4aef0775"
> -SRC_URI[sha256sum] = "3ed776627181cb9c1c9ba33f94a6319084be2e9ec9c23dd61ce784c4f602cf05"
> +SRC_URI[md5sum] = "e48fcfdb2162e77d72c2a83432d537ca"
> +SRC_URI[sha256sum] = "07019d38ae98fb107c79dbb3690cfadff877f153b8c4970e3a30d2e59aa66baa"
>
Acked-by: Aníbal Limón <anibal.limon@linux.intel.com>
Cheers,
alimon
prev parent reply other threads:[~2015-05-04 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 8:09 [PATCH] dpkg: upgrade to 1.17.25 rongqing.li
2015-05-04 15:14 ` Aníbal Limón [this message]
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=55478CD5.5060303@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rongqing.li@windriver.com \
/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.