From: Douglas Royds <douglas.royds@taitradio.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssl: fix for CVE-2010-5298
Date: Thu, 22 May 2014 13:42:22 +1200 [thread overview]
Message-ID: <537D55FE.8090603@taitradio.com> (raw)
In-Reply-To: <1400482838-7751-1-git-send-email-rongqing.li@windriver.com>
On 19/05/14 19:00, rongqing.li@windriver.com wrote:
> From: Yue Tao <Yue.Tao@windriver.com>
>
> Race condition in the ssl3_read_bytes function in s3_pkt.c in OpenSSL
> through 1.0.1g, when SSL_MODE_RELEASE_BUFFERS is enabled, allows remote
> attackers to inject data across sessions or cause a denial of service
> (use-after-free and parsing error) via an SSL connection in a
> multithreaded environment.
>
> http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-5298
>
> Signed-off-by: Yue Tao <Yue.Tao@windriver.com>
> Signed-off-by: Roy Li <rongqing.li@windriver.com>
> ---
> .../openssl-1.0.1e/openssl-CVE-2010-5298.patch | 24 ++++++++++++++++++++
> 1 file changed, 24 insertions(+)
> create mode 100644 meta/recipes-connectivity/openssl/openssl-1.0.1e/openssl-CVE-2010-5298.patch
>
> diff --git a/meta/recipes-connectivity/openssl/openssl-1.0.1e/openssl-CVE-2010-5298.patch b/meta/recipes-connectivity/openssl/openssl-1.0.1e/openssl-CVE-2010-5298.patch
> new file mode 100644
> index 0000000..417a774
> --- /dev/null
> +++ b/meta/recipes-connectivity/openssl/openssl-1.0.1e/openssl-CVE-2010-5298.patch
> @@ -0,0 +1,24 @@
> +openssl fix for CVE-2010-5298
> +
> +Upstream-Status: Backport
> +
> +Race condition in the ssl3_read_bytes function in s3_pkt.c in OpenSSL
> +through 1.0.1g, when SSL_MODE_RELEASE_BUFFERS is enabled, allows remote
> +attackers to inject data across sessions or cause a denial of service
> +(use-after-free and parsing error) via an SSL connection in a
> +multithreaded environment.
> +
> +http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-5298
> +
> +Signed-off-by: Yue Tao <Yue.Tao@windriver.com>
> +--- a/ssl/s3_pkt.c
> ++++ b/ssl/s3_pkt.c
> +@@ -1013,7 +1013,7 @@ start:
> + {
> + s->rstate=SSL_ST_READ_HEADER;
> + rr->off=0;
> +- if (s->mode & SSL_MODE_RELEASE_BUFFERS)
> ++ if (s->mode & SSL_MODE_RELEASE_BUFFERS && s->s3->rbuf.left == 0)
> + ssl3_release_read_buffer(s);
> + }
> + }
This patch file appears to be orphaned in openssl-1.0.1e/, when the
current version is 1.0.1g.
Also, there is no file://openssl-CVE-2010-5298.patch entry in the SRC_URI.
Was this deliberate? Am I missing something?
next prev parent reply other threads:[~2014-05-22 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 7:00 [PATCH] openssl: fix for CVE-2010-5298 rongqing.li
2014-05-22 1:42 ` Douglas Royds [this message]
2014-05-22 5:24 ` Rongqing Li
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=537D55FE.8090603@taitradio.com \
--to=douglas.royds@taitradio.com \
--cc=openembedded-core@lists.openembedded.org \
/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