manager.c: Restrict ListCategories to the configuration directory.

When using the ListCategories AMI action, it was possible to traverse
upwards through the directories to files outside of the configured
configuration directory. This action is now restricted to the configured
directory and an error will now be returned if the specified file is
outside of this limitation.

Resolves: #GHSA-33x6-fj46-6rfh

UserNote: The ListCategories AMI action now restricts files to the
configured configuration directory.

diff --git a/main/manager.c b/main/manager.c
index e599da71a0544b7425a512b009d5af7f02401c4c..ba593660ed6692e9d503d07f3ff4004f06625e8c 100644 (file)
--- a/main/manager.c
+++ b/main/manager.c
@@ -3899,12 +3899,22 @@ static int action_listcategories(struct mansession *s, const struct message *m)
        struct ast_category *category = NULL;
        struct ast_flags config_flags = { CONFIG_FLAG_WITHCOMMENTS | CONFIG_FLAG_NOCACHE };
        int catcount = 0;
+       int ret = 0;
 
        if (ast_strlen_zero(fn)) {
                astman_send_error(s, m, "Filename not specified");
                return 0;
        }
 
+       ret = restrictedFile(fn);
+       if (ret == 1) {
+               astman_send_error(s, m, "File requires escalated priveledges");
+               return 0;
+       } else if (ret == -1) {
+               astman_send_error(s, m, "Config file not found");
+               return 0;
+       }
+
        if (!(cfg = ast_config_load2(fn, "manager", config_flags))) {
                astman_send_error(s, m, "Config file not found");
                return 0;