After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 335942 - clock-applet executable stack (security best-practice failure)
clock-applet executable stack (security best-practice failure)
Status: RESOLVED NOTGNOME
Product: gnome-panel
Classification: Other
Component: clock
2.14.x
Other Linux
: Normal enhancement
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-25 11:44 UTC by Sebastien Bacher
Modified: 2006-06-14 16:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2006-03-25 11:44:22 UTC
That bug has been described on https://launchpad.net/malone/bugs/34130

"lsmemmap.sh shows clock-applet has an executable stack on x86-64. This is a security best-practice failure: shellcode injection into the stack is possible now that it is executable. Note that in the case of clock-applet there is theoretically no way to elevate privileges and thus this is very minor.

task 5169 (/usr/lib/gnome-panel/clock-applet)
  7fffffa56000-7fffffa6a000 rwxp 7fffffa56000 00:00 0 [stack]

Please note that this is not a security vulnerability; it is a failure to execute security best practices. By correcting this, certain real vulnerabilities will become difficult or impossible to exploit beyond basic denial of service.

The most likely cause of this is the use of gcc nested functions in clock-applet.

See also bug #34129 which has the script I used as an attachment.

Marking minor low priority, as this is basically not exploitable in theory. It would be nice to see this corrected but not practically important."
Comment 1 Vincent Untz 2006-03-25 14:29:17 UTC
I've compiled the clock applet with -ansi -pedantic and there's no problem. Could this be evolution-data-server that have this problem?
Comment 2 John Richard Moser 2006-06-10 15:36:26 UTC
This happens because of libgcrypt.so.11 having a set PT_GNU_STACK marking.  I have noted in Ubuntu to correct this by building libgcrypt with --disable-asm.
Comment 3 John Richard Moser 2006-06-14 16:22:40 UTC
Also fixable by building with assembly but putting a .note.GNU-stack in as described on ubuntu bug #49192
Comment 4 Sebastien Bacher 2006-06-14 16:49:25 UTC
closing as NOTGNOME since that's not a panel issue