execstack --set-execstack<path> Aborted (core dump)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
prelink (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Reproducer:
$ cp /bin/ls /tmp
$ execstack --set-execstack /tmp/ls
execstack: dso.c:877: reopen_dso: Assertion `dso->shdr[
Aborted (core dumped)
[134]
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: execstack 0.0.20131005-1
ProcVersionSign
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct 31 16:35:17 2019
InstallationDate: Installed on 2016-10-01 (1125 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
TERM=xterm-
XDG_RUNTIME_
PATH=(custom, user)
SourcePackage: prelink
UpgradeStatus: Upgraded to eoan on 2019-10-27 (4 days ago)
$ hardening-check /tmp/ls
/tmp/ls:
Position Independent Executable: yes
Stack protected: yes
Fortify Source functions: yes (some protected functions found)
Read-only relocations: yes
Immediate binding: yes
Stack clash protection: yes
Control flow integrity: yes
On older releases, we can use --set-execstack on /bin/ls. hardening-check is different:
$ hardening-check /tmp/ls-bionic clash-protectio n instructions found
/tmp/ls-bionic:
Position Independent Executable: yes
Stack protected: yes
Fortify Source functions: yes (some protected functions found)
Read-only relocations: yes
Immediate binding: yes
Stack clash protection: unknown, no -fstack-
Control flow integrity: unknown, no -fcf-protection instructions found!