From: yzhu1 <Yanjun.Zhu@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libproxy: Fix for CVE-2012-4504
Date: Wed, 28 Nov 2012 17:58:39 +0800 [thread overview]
Message-ID: <50B5E04F.9040003@windriver.com> (raw)
In-Reply-To: <2179675.GOD3EuFAz2@helios>
On 11/28/2012 05:44 PM, Paul Eggleton wrote:
> 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?
OK.
Thanks a lot.
Zhu Yanjun
> Thanks,
> Paul
>
next prev parent reply other threads:[~2012-11-28 10:12 UTC|newest]
Thread overview: 9+ 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
2012-11-28 9:58 ` yzhu1 [this message]
2012-11-28 10:13 ` [oe][PATCH] " yanjun.zhu
2012-11-29 17:45 ` Saul Wold
2012-11-30 5:42 ` [PATCH 1/1] " yanjun.zhu
2012-11-30 5:44 ` yzhu1
2012-11-30 6:04 ` yanjun.zhu
2012-11-30 11:08 ` yanjun.zhu
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=50B5E04F.9040003@windriver.com \
--to=yanjun.zhu@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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.