From: Alex Sassmannshausen <alex@pompo.co>
To: Leo Famulari <leo@famulari.name>
Cc: 27808@debbugs.gnu.org
Subject: bug#27808: PHP CVE-2017-11144, CVE-2017-11145, CVE-2017-11362
Date: Tue, 25 Jul 2017 17:26:35 +0200 [thread overview]
Message-ID: <87k22wo7v8.fsf@pompo.co> (raw)
In-Reply-To: <20170724185744.GA4997@jasmine.lan>
Hi Leo,
I've just submitted a patch to update PHP to version 7.1.7, which
resolves the CVEs. Unfortunately PHP has 4 test errors on my machine
(but also on the previous version), so I could not fully build it
(disabling tests results in a working version of PHP).
The relevant patch is at 27826. If someone could try building it, on
x86_64 then we could be sure it's just my local environment that messes
things up…
Alex
Leo Famulari writes:
> Apparently our PHP package is vulnerable to CVE-2017-11144,
> CVE-2017-11145, and CVE-2017-11362:
>
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11144
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11145
>
> This one looks especially bad:
>
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11362
>
> Can someone please take a look at this?
next prev parent reply other threads:[~2017-07-25 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 18:57 bug#27808: PHP CVE-2017-11144, CVE-2017-11145, CVE-2017-11362 Leo Famulari
2017-07-25 15:26 ` Alex Sassmannshausen [this message]
2017-07-25 18:41 ` Leo Famulari
2017-07-25 19:44 ` Alex Sassmannshausen
2017-07-31 15:32 ` bug#27808: [bug#27826] " Ludovic Courtès
2017-07-31 16:22 ` Alex Sassmannshausen
2017-08-20 20:10 ` Alex Sassmannshausen
2017-08-20 20:11 ` Alex Sassmannshausen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k22wo7v8.fsf@pompo.co \
--to=alex@pompo.co \
--cc=27808@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).