aboutsummaryrefslogtreecommitdiff
path: root/sway/commands/ipc.c
diff options
context:
space:
mode:
authorJerzi Kaminsky <JerziKaminsky@users.noreply.github.com>2017-04-16 09:30:14 +0300
committerJerzi Kaminsky <JerziKaminsky@users.noreply.github.com>2017-04-16 17:09:53 +0300
commit2ad8850398693cb572152e6d97c59de371996273 (patch)
tree21abe14fe200099fffe5de9b7770cf2ca921e371 /sway/commands/ipc.c
parentc9694ee63d451da62dc50b234b3080a35a40e844 (diff)
downloadsway-2ad8850398693cb572152e6d97c59de371996273.zip
sway-2ad8850398693cb572152e6d97c59de371996273.tar.gz
sway-2ad8850398693cb572152e6d97c59de371996273.tar.bz2
Handle symlinks as IPC security targets
- When policies are allocated, the ipc target path goes through symlink resolution. The result is used as the canonical for matching pids to policies at runtime. In particular, this matches up with the target of the `/proc/<pid>/exe`. - There's a possible race condition if this isn't done correctly, read below. Originally, validate_ipc_target() always tried to resolve its argument for symlinks, and returned a parogram target string if it validates. This created a possible race condition with security implications. The problem is that get_feature_policy() first independently resolved the policy target in order to check whether a policy already exists. If it didn't find any, it called alloc_feature_policy() which called validate_ipc_target() which resolved the policy target again. In the time between the two checks, the symlink could be altered, and a lucky attacker could fool the program into thinking that a policy doesn't exist for a target, and then switch the symlink to point at another file. At the very least this could allow him to create two policies for the same program target, and possibly to bypass security by associating the permissions for one target with another, or force default permissions to apply to a target for which a more specific rule has been configured. So we don't that. Instead, the policy target is resolved once and that result is used for the rest of the lookup/creation process.
Diffstat (limited to 'sway/commands/ipc.c')
-rw-r--r--sway/commands/ipc.c10
1 files changed, 9 insertions, 1 deletions
diff --git a/sway/commands/ipc.c b/sway/commands/ipc.c
index 8a7b849..f0b3035 100644
--- a/sway/commands/ipc.c
+++ b/sway/commands/ipc.c
@@ -1,3 +1,4 @@
+#define _XOPEN_SOURCE 500
#include <stdio.h>
#include <string.h>
#include "sway/security.h"
@@ -18,8 +19,14 @@ struct cmd_results *cmd_ipc(int argc, char **argv) {
return error;
}
- const char *program = argv[0];
+ char *program = NULL;
+ if (!strcmp(argv[0], "*")) {
+ program = strdup(argv[0]);
+ } else if (!(program = resolve_path(argv[0]))) {
+ return cmd_results_new(
+ CMD_INVALID, "ipc", "Unable to resolve IPC Policy target.");
+ }
if (config->reading && strcmp("{", argv[1]) != 0) {
return cmd_results_new(CMD_INVALID, "ipc",
"Expected '{' at start of IPC config definition.");
@@ -32,6 +39,7 @@ struct cmd_results *cmd_ipc(int argc, char **argv) {
current_policy = alloc_ipc_policy(program);
list_add(config->ipc_policies, current_policy);
+ free(program);
return cmd_results_new(CMD_BLOCK_IPC, NULL, NULL);
}