Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54857 - [libffi] [Security] arbitrary code execution (CVE-2017-1000376)

Attached to Project: Arch Linux
Opened by Pablo Lezaeta (Jristz) - Tuesday, 18 July 2017, 05:33 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 18 July 2017, 05:46 GMT
Task Type Bug Report
Category Security
Status Assigned
Assigned To Bartłomiej Piotrowski (Barthalion)
Levente Polyak (anthraxx)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Summary
=======

The package libffi is vulnerable to arbitrary code execution via CVE-2017-1000376.

Guidance
========

There is a patch on debian 3.2.1-4 with the fix so we only need take the patch I think.

References
==========

https://security.archlinux.org/AVG-310
https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt
This task depends upon

Comment by Pablo Lezaeta (Jristz) - Wednesday, 19 July 2017, 22:48 GMT
Ok I check the debian bugtracker, to fix this is need first build the package with --enable-pax_emutramp and also add 01_add_missing_GNU_STACK_markings patch but the only relevants patches on debian source are the one I attach so I think either adding the flag and the patches will fix the issue.

Yet the other option is the well know -fstack-check=specific flag for all linked and this package... so I will go to debian and take the 2 patches (there is a three for aarm64 so is unnedded here).
Comment by Levente Polyak (anthraxx) - Thursday, 20 July 2017, 09:42 GMT
-fstack-check=specific itself does not fully mitigate the issue, its broken by design
Comment by Pablo Lezaeta (Jristz) - Sunday, 23 July 2017, 02:59 GMT
you say it, "fully" which is better than nothing.

The 3th option is just wait until the fstack-check get fixed and rebuild the linked packaged plus this one.

Loading...