From: yzhu1 <Yanjun.Zhu@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] python: fix for Security Advisory - python - CVE-2012-2135
Date: Fri, 30 Nov 2012 10:49:55 +0800 [thread overview]
Message-ID: <50B81ED3.8020303@windriver.com> (raw)
In-Reply-To: <1547659.oHFHv4PiYI@helios>
On 11/29/2012 10:07 PM, Paul Eggleton wrote:
> On Friday 16 November 2012 16:53:42 yanjun.zhu wrote:
>> The utf-16 decoder in Python 3.1 through 3.3 does not update the
>> aligned_end variable after calling the unicode_decode_call_errorhandler
>> function, which allows remote attackers to obtain sensitive information
>> (process memory) or cause a denial of service (memory corruption and crash)
>> via unspecified vectors.
>>
>> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-2135
>>
>> Signed-off-by: yanjun.zhu <yanjun.zhu@windriver.com>
>> ---
>> .../python/python/python-2.7.2-CVE-2012-2135.patch | 12 ++++++++++++
>> recipes-devtools/python/python_2.7.2.bbappend | 1 +
>> 2 files changed, 13 insertions(+), 0 deletions(-)
>> create mode 100644
>> recipes-devtools/python/python/python-2.7.2-CVE-2012-2135.patch
> This patch is also against OE-Core, could you send this to the OE-Core list as
> well?
OK. I will follow your advice.
Thanks a lot.
Zhu Yanjun
> Thanks,
> Paul
>
prev parent reply other threads:[~2012-11-30 3:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yes>
2011-04-13 22:08 ` [PATCH 2/2] ltp-ddt: New recipe to build ltp-ddt test tool Carlos Hernandez
2012-11-16 8:53 ` [PATCH] python: fix for Security Advisory - python - CVE-2012-2135 yanjun.zhu
2012-11-16 12:21 ` Otavio Salvador
2012-11-19 2:26 ` yzhu1
2012-11-19 2:36 ` yzhu1
2012-11-19 10:21 ` Otavio Salvador
2012-11-29 14:07 ` Paul Eggleton
2012-11-30 2:49 ` yzhu1 [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=50B81ED3.8020303@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox