All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Carter <jwcart2@gmail.com>
To: selinux@vger.kernel.org
Cc: nicolas.iooss@m4x.org, James Carter <jwcart2@gmail.com>
Subject: [PATCH 08/11 v2] libsepol/cil: Allow permission expressions when using map classes
Date: Mon, 19 Apr 2021 11:15:54 -0400	[thread overview]
Message-ID: <20210419151557.87561-9-jwcart2@gmail.com> (raw)
In-Reply-To: <20210419151557.87561-1-jwcart2@gmail.com>

The following policy will cause a segfault:
  (class CLASS (PERM))
  (class C (P1 P2 P3))
  (classorder (CLASS C))
  (sid SID)
  (sidorder (SID))
  (user USER)
  (role ROLE)
  (type TYPE)
  (category CAT)
  (categoryorder (CAT))
  (sensitivity SENS)
  (sensitivityorder (SENS))
  (sensitivitycategory SENS (CAT))
  (allow TYPE self (CLASS (PERM)))
  (roletype ROLE TYPE)
  (userrole USER ROLE)
  (userlevel USER (SENS))
  (userrange USER ((SENS)(SENS (CAT))))
  (sidcontext SID (USER ROLE TYPE ((SENS)(SENS))))

  (classmap CM (PM1 PM2 PM3))
  (classmapping CM PM1 (C (P1)))
  (classmapping CM PM2 (C (P2)))
  (classmapping CM PM3 (C (P3)))
  (allow TYPE self (CM (and (all) (not PM2))))

The problem is that, while permission expressions are allowed for
normal classes, map classes are expected to only have permission
lists and no check is done to verify that only a permission list
is being used.

When the above policy is parsed, the "and" and "all" are seen as
expression operators, but when the map permissions are converted to
normal class and permissions, the permission expression is assumed
to be a list of datums and since the operators are not datums a
segfault is the result.

There is no reason to limit map classes to only using a list of
permissions and, in fact, it would be better to be able to use them
in the same way normal classes are used.

Allow permissions expressions to be used for map classes by first
evaluating the permission expression and then converting the
resulting list to normal classes and permissions.

Signed-off-by: James Carter <jwcart2@gmail.com>
---
 libsepol/cil/src/cil_post.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/libsepol/cil/src/cil_post.c b/libsepol/cil/src/cil_post.c
index fd4758dc..05842b64 100644
--- a/libsepol/cil/src/cil_post.c
+++ b/libsepol/cil/src/cil_post.c
@@ -2137,6 +2137,10 @@ static int __evaluate_classperms_list(struct cil_list *classperms, struct cil_db
 				}
 			} else { /* MAP */
 				struct cil_list_item *i = NULL;
+				rc = __evaluate_classperms(cp, db);
+				if (rc != SEPOL_OK) {
+					goto exit;
+				}
 				cil_list_for_each(i, cp->perms) {
 					struct cil_perm *cmp = i->data;
 					rc = __evaluate_classperms_list(cmp->classperms, db);
-- 
2.26.3


  parent reply	other threads:[~2021-04-19 15:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 15:15 [PATCH 00/11 v2] Various CIL patches James Carter
2021-04-19 15:15 ` [PATCH 01/11 v2] libsepol/cil: Fix out-of-bound read of file context pattern ending with "\" James Carter
2021-04-19 15:15 ` [PATCH 02/11 v2] libsepol/cil: Destroy classperms list when resetting classpermission James Carter
2021-04-19 15:15 ` [PATCH 03/11 v2] libsepol/cil: Destroy classperm list when resetting map perms James Carter
2021-04-19 15:15 ` [PATCH 04/11 v2] libsepol/cil: cil_reset_classperms_set() should not reset classpermission James Carter
2021-04-19 15:15 ` [PATCH 05/11 v2] libsepol/cil: Set class field to NULL when resetting struct cil_classperms James Carter
2021-04-19 15:15 ` [PATCH 06/11 v2] libsepol/cil: More strict verification of constraint leaf expressions James Carter
2021-04-19 15:15 ` [PATCH 07/11 v2] libsepol/cil: Exit with an error if declaration name is a reserved word James Carter
2021-04-19 15:15 ` James Carter [this message]
2021-04-19 15:15 ` [PATCH 09/11 v2] libsepol/cil: Refactor helper function for cil_gen_node() James Carter
2021-04-19 15:15 ` [PATCH 10/11 v2] libsepol/cil: Create function cil_add_decl_to_symtab() and refactor James Carter
2021-04-19 15:15 ` [PATCH 11/11 v2] libsepol/cil: Move check for the shadowing of macro parameters James Carter
2021-04-19 18:24 ` [PATCH 00/11 v2] Various CIL patches James Carter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210419151557.87561-9-jwcart2@gmail.com \
    --to=jwcart2@gmail.com \
    --cc=nicolas.iooss@m4x.org \
    --cc=selinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.