libffi requests an executable stack allowing attackers to more easily trigger arbitrary code execution by overwriting the stack. Please note that libffi is used by a number of other libraries. It was previously stated that this affects libffi version 3.2.1 but this appears to be incorrect. libffi prior to version 3.1 on 32 bit x86 systems was vulnerable, and upstream is believed to have fixed this issue in version 3.1.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Link | Tags |
---|---|
https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt | third party advisory mailing list |
https://access.redhat.com/security/cve/CVE-2017-1000376 | third party advisory |
http://www.debian.org/security/2017/dsa-3889 | third party advisory vendor advisory |
https://www.oracle.com/security-alerts/cpujan2020.html | third party advisory |