From: Saul Wold <sgw@linux.intel.com>
To: "yanjun.zhu" <yanjun.zhu@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] Python: Fix for CVE-2012-2135
Date: Fri, 30 Nov 2012 00:05:30 -0800 [thread overview]
Message-ID: <50B868CA.4020906@linux.intel.com> (raw)
In-Reply-To: <1354249830-25918-1-git-send-email-yanjun.zhu@windriver.com>
On 11/29/2012 08:30 PM, yanjun.zhu wrote:
> From: "yanjun.zhu" <yanjun.zhu@windriver.com>
>
> Reference:http://http://bugs.python.org/issue14579
>
> 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 | 22 ++++++++++++++++++++++
> meta/recipes-devtools/python/python_2.7.2.bb | 1 +
> 2 files changed, 23 insertions(+)
> create mode 100644 meta/recipes-devtools/python/python/python-2.7.2-CVE-2012-2135.patch
>
> diff --git a/meta/recipes-devtools/python/python/python-2.7.2-CVE-2012-2135.patch b/meta/recipes-devtools/python/python/python-2.7.2-CVE-2012-2135.patch
> new file mode 100644
> index 0000000..bb9719e
> --- /dev/null
> +++ b/meta/recipes-devtools/python/python/python-2.7.2-CVE-2012-2135.patch
> @@ -0,0 +1,22 @@
> +Reference:http://http://bugs.python.org/issue14579
> +
> +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
Need Upstream-Status: Like all the other CVE patches you have
submitted, please fix this. I appreciate the work you are doing, but
please include Upstream-Status, are these backport, or pending?
Sau!
> +Signed-off-by: yanjun.zhu <yanjun.zhu@windriver.com>
> +diff -urpN a/Objects/unicodeobject.c b/Objects/unicodeobject.c
> +--- a/Objects/unicodeobject.c 2012-11-12 16:25:33.000000000 +0800
> ++++ b/Objects/unicodeobject.c 2012-11-12 16:26:22.000000000 +0800
> +@@ -2568,7 +2568,7 @@ PyUnicode_DecodeUTF16Stateful(const char
> + }
> +
> + /* UTF-16 code pair: */
> +- if (q >= e) {
> ++ if (e - q < 2) {
> + errmsg = "unexpected end of data";
> + startinpos = (((const char *)q)-2)-starts;
> + endinpos = ((const char *)e)-starts;
> diff --git a/meta/recipes-devtools/python/python_2.7.2.bb b/meta/recipes-devtools/python/python_2.7.2.bb
> index 2adb4e4..9dabfb7 100644
> --- a/meta/recipes-devtools/python/python_2.7.2.bb
> +++ b/meta/recipes-devtools/python/python_2.7.2.bb
> @@ -24,6 +24,7 @@ SRC_URI += "\
> file://setuptweaks.patch \
> file://check-if-target-is-64b-not-host.patch \
> file://search_db_h_in_inc_dirs_and_avoid_warning.patch \
> + file://python-2.7.2-CVE-2012-2135.patch \
> "
>
> S = "${WORKDIR}/Python-${PV}"
>
next prev parent reply other threads:[~2012-11-30 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3450>
2012-11-30 4:30 ` [PATCH 1/1] Python: Fix for CVE-2012-2135 yanjun.zhu
2012-11-30 8:05 ` Saul Wold [this message]
2012-12-06 13:01 ` Burton, Ross
2012-12-07 1:45 ` yzhu1
2012-11-30 10:47 ` yanjun.zhu
2012-11-30 11:02 ` yanjun.zhu
2012-11-30 11:23 ` yanjun.zhu
2012-11-30 11:29 ` yanjun.zhu
2012-11-30 18:54 ` [PATCH 1/1] Python: Fix for CVE-2012-2135 (for denzil) Saul Wold
2012-11-30 23:21 ` Scott Garman
2013-03-04 4:35 ` [PATCH 1/1] Python: Fix for CVE-2012-2135 yanjun.zhu
2013-03-04 10:46 ` Burton, Ross
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=50B868CA.4020906@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@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 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.