Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "yanjun.zhu" <yanjun.zhu@windriver.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libproxy: Fix for CVE-2012-4504
Date: Wed, 28 Nov 2012 09:44:57 +0000	[thread overview]
Message-ID: <2179675.GOD3EuFAz2@helios> (raw)
In-Reply-To: <1354070578-5401-1-git-send-email-yanjun.zhu@windriver.com>

Hi there,

On Wednesday 28 November 2012 10:42:58 yanjun.zhu wrote:
> From: "yanjun.zhu" <yanjun.zhu@windriver.com>
> 
> Reference:https://code.google.com/p/libproxy/source/detail?r=853
> 
> Stack-based buffer overflow in the url::get_pac function in url.cpp
> in libproxy 0.4.x before 0.4.9 allows remote servers to have an
> unspecified impact via a large proxy.pac file.
> 
> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-4504
> 
> Signed-off-by: yanjun.zhu <yanjun.zhu@windriver.com>
> ---
>  recipes-support/libproxy/libproxy_0.4.7.bbappend          |  5 +++++
>  .../libproxy/patches/libproxy-0.4.7-CVE-2012-4504.patch   | 15

Thanks for submitting this, but this is not the correct mailing list for 
patches against OE-Core. Could you please apply this patch to OE-Core master 
and then re-send the result to openembedded-core@lists.openembedded.org?

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-11-28 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3487>
2012-11-28  2:42 ` [PATCH] libproxy: Fix for CVE-2012-4504 yanjun.zhu
2012-11-28  9:44   ` Paul Eggleton [this message]
2012-11-28  9:58     ` yzhu1

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=2179675.GOD3EuFAz2@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=yanjun.zhu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox