From: akuster808 <akuster808@gmail.com>
To: wenzong.fan@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] subversion: fix CVE-2015-3184, CVE-2015-3187
Date: Tue, 17 Nov 2015 17:26:24 -0800 [thread overview]
Message-ID: <564BD3C0.8000900@gmail.com> (raw)
In-Reply-To: <cover.1447738630.git.wenzong.fan@windriver.com>
On 11/16/2015 09:38 PM, wenzong.fan@windriver.com wrote:
> From: Wenzong Fan <wenzong.fan@windriver.com>
>
> The following changes since commit d9aabf9639510fdb3e2ccc21ba5ae4aa9f6e4a57:
>
> gcc: Drop 4.8 (2015-11-16 14:59:18 +0000)
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib wenzong/svn
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/svn
>
> Wenzong Fan (2):
Thanks.
> subversion: fix CVE-2015-3184
> subversion: fix CVE-2015-3187
These two fixes only affect Apache.
Apache version < 2.4.16 will need the following fix too.
CVE-2015-3185 httpd: ap_some_auth_required() does not properly indicate
authenticated request in 2.4
This affects fido.
- armin
>
> .../subversion-CVE-2015-3184.patch | 2094 ++++++++++++++++++++
> .../subversion-CVE-2015-3187.patch | 346 ++++
> .../subversion/subversion_1.8.13.bb | 2 +
> 3 files changed, 2442 insertions(+)
> create mode 100644 meta/recipes-devtools/subversion/subversion-1.8.13/subversion-CVE-2015-3184.patch
> create mode 100644 meta/recipes-devtools/subversion/subversion-1.8.13/subversion-CVE-2015-3187.patch
>
next prev parent reply other threads:[~2015-11-18 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 5:38 [PATCH 0/2] subversion: fix CVE-2015-3184, CVE-2015-3187 wenzong.fan
2015-11-17 5:38 ` [PATCH 1/2] subversion: fix CVE-2015-3184 wenzong.fan
2015-11-17 5:38 ` [PATCH 2/2] subversion: fix CVE-2015-3187 wenzong.fan
2015-11-18 1:26 ` akuster808 [this message]
2015-11-27 6:20 ` [PATCH 0/2] subversion: fix CVE-2015-3184, CVE-2015-3187 wenzong fan
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=564BD3C0.8000900@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wenzong.fan@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