From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Flex security update: RCE in generated code (CVE-2016-6354)
Date: Sat, 27 Aug 2016 23:48:10 +0200 [thread overview]
Message-ID: <87poot7ujp.fsf@gnu.org> (raw)
In-Reply-To: <20160826224959.GA8478@jasmine> (Leo Famulari's message of "Fri, 26 Aug 2016 18:49:59 -0400")
Hello!
Leo Famulari <leo@famulari.name> skribis:
> On Fri, Aug 26, 2016 at 06:14:26PM -0400, Leo Famulari wrote:
>> Subject: [PATCH] gnu: flex: Fix CVE-2016-6354.
>>
>> * gnu/packages/flex.scm (flex)[replacement]: New field.
>> (flex/fixed): New variable.
>> * gnu/packages/patches/flex-CVE-2016-6354.patch: New file.
>> * gnu/local.mk (dist_patch_DATA): Add it.
>
> As Mark pointed out on #guix, bugs in flex's generated code can not be
> addressed with a graft.
Indeed. We should add this patch to ‘core-updates’ and start building
it (I haven’t checked the status of the various branches, though.)
> Also, the upstream tarballs that we build from often contain code
> generated by flex.
Yes, and finding out which tarballs contain vulnerable lexers (or
contain Flex-generated stuff at all) sounds difficult.
Maybe people have developed scripts to help with that?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-08-27 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 22:14 Flex security update: RCE in generated code (CVE-2016-6354) Leo Famulari
2016-08-26 22:49 ` Leo Famulari
2016-08-27 21:48 ` Ludovic Courtès [this message]
2016-08-28 0:54 ` Leo Famulari
2016-08-28 9:41 ` Efraim Flashner
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=87poot7ujp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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).