Re: capget() overflows buffers.

From: Andrew G. Morgan
Date: Thu May 22 2008 - 18:53:00 EST

Hash: SHA1

Chris Wright wrote:
| * Chris Wright (chrisw@xxxxxxxxxxxx) wrote:
|> Yes, this thing is broken.
| Andrew, I think this should be considered a serious problem. The
| interface ABI is stable for old programs, and fine for anything new
| or old that's using libcap. But the API has changed subtly (taking a
| pointer to a blob, to a pointer to an array of blobs), and is easily
| broken for programs recompiled against new headers not using libcap.

[There is a warning about this issue in the kernel header file.]

The kernel is not crashing, the application is...

If you take this compiled binary, that crashes on 2.6.25, and try to run
it on 2.6.24 it will fail there too - since the magic its 'forcing' is
not valid on that kernel. So the compiled 'binary' we're discussing does
not have an existence proof that it will successfully run anywhere.

In point of fact, the kernel is binary compatible with old binaries. The
problem is that _LINUX_CAPABILITY_VERSION #define now points to _2
instead of _1 by default and Squid etc., are not paying attention to the
value of the new magic cookie but expecting the previous revision of the
ABI to work.

As such, I don't agree that there is a problem with the ABI, and I don't
agree with your assertion about things being broken. I maintain there is
a problem with the application source code.

One 'solution' is to force everyone to notice at compile time by simply
removing the definition of _LINUX_CAPABILITY_VERSION and force all new
source code to be explicit about which ABI it wants to use...



| For the squid issue at least it does capget/capset, so it's likely to
| write back in capset the caps it got in capget (when it doesn't hit
| glibc heap overflow protection).
| But bind, for example, could have garbage in the upper 32bits on a 64bit
| caps system that does not HAVE_LIBCAP:
| (Note: snipped it down to make it readable, removed some ifdef
| linux_setcaps(cap_t caps) {
| struct __user_cap_header_struct caphead;
| struct __user_cap_data_struct cap; <-- just one set of u32s
| <snip>
| memset(&caphead, 0, sizeof(caphead));
| caphead.version = _LINUX_CAPABILITY_VERSION; <-- v2
| = 0;
| memset(&cap, 0, sizeof(cap));
| cap.effective = caps;
| cap.permitted = caps;
| cap.inheritable = 0; <-- fill in just that set
| <snip>
| if (syscall(SYS_capset, &caphead, &cap) < 0) {
| ^^^ kernel pulls 2 sets of
| u32s, send is just junk from
| stack
| For the squid case that Bojan described:
| (Note: snipped it down again)
| restoreCapabilities(int keep)
| {
| cap_user_header_t head = (cap_user_header_t) xcalloc(1,
| cap_user_data_t cap = (cap_user_data_t) xcalloc(1,
| head->version = _LINUX_CAPABILITY_VERSION;
| if (capget(head, cap) != 0) {
| <snip>
| head->pid = 0;
| cap->inheritable = 0;
| cap->effective = (1 << CAP_NET_BIND_SERVICE);
| <snip>
| if (!keep)
| cap->permitted &= cap->effective;
| if (capset(head, cap) != 0) {
| I don't see a nice solution, short reverting, and adding a new set of
| syscalls to support 64-bit.
| thanks,
| -chris
Version: GnuPG v1.2.6 (GNU/Linux)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at