Re: [PATCH] lsm: copy comm before calling audit_log to avoid race in string printing

2015-04-14 Thread James Morris
On Tue, 14 Apr 2015, Richard Guy Briggs wrote:

> When task->comm is passed directly to audit_log_untrustedstring() without
> getting a copy or using the task_lock, there is a race that could happen that
> would output a NULL (\0) in the middle of the output string that would
> effectively truncate the rest of the report text after the comm= field in the
> audit log message, losing fields.
> 
> Using get_task_comm() to get a copy while acquiring the task_lock to prevent
> this and to prevent the result from being a mixture of old and new values of
> comm would incur potentially unacceptable overhead, considering that the value
> can be influenced by userspace and therefore untrusted anyways.
> 
> Copy the value before passing it to audit_log_untrustedstring() ensures that a
> local copy is used to calculate the length *and* subsequently printed.  Even 
> if
> this value contains a mix of old and new values, it will only calculate and
> copy up to the first NULL, preventing the rest of the audit log message being
> truncated.
> 
> Use a second local copy of comm to avoid a race between the first and second
> calls to audit_log_untrustedstring() with comm.
> 
> Reported-by: Tetsuo Handa 
> Signed-off-by: Richard Guy Briggs 

Applied.

-- 
James Morris


--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit


[PATCH] lsm: copy comm before calling audit_log to avoid race in string printing

2015-04-14 Thread Richard Guy Briggs
When task->comm is passed directly to audit_log_untrustedstring() without
getting a copy or using the task_lock, there is a race that could happen that
would output a NULL (\0) in the middle of the output string that would
effectively truncate the rest of the report text after the comm= field in the
audit log message, losing fields.

Using get_task_comm() to get a copy while acquiring the task_lock to prevent
this and to prevent the result from being a mixture of old and new values of
comm would incur potentially unacceptable overhead, considering that the value
can be influenced by userspace and therefore untrusted anyways.

Copy the value before passing it to audit_log_untrustedstring() ensures that a
local copy is used to calculate the length *and* subsequently printed.  Even if
this value contains a mix of old and new values, it will only calculate and
copy up to the first NULL, preventing the rest of the audit log message being
truncated.

Use a second local copy of comm to avoid a race between the first and second
calls to audit_log_untrustedstring() with comm.

Reported-by: Tetsuo Handa 
Signed-off-by: Richard Guy Briggs 
---
 security/lsm_audit.c |   15 +--
 1 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/security/lsm_audit.c b/security/lsm_audit.c
index 69fdf3b..b526ddc 100644
--- a/security/lsm_audit.c
+++ b/security/lsm_audit.c
@@ -211,7 +211,7 @@ static inline void print_ipv4_addr(struct audit_buffer *ab, 
__be32 addr,
 static void dump_common_audit_data(struct audit_buffer *ab,
   struct common_audit_data *a)
 {
-   struct task_struct *tsk = current;
+   char comm[sizeof(current->comm)];
 
/*
 * To keep stack sizes in check force programers to notice if they
@@ -220,8 +220,8 @@ static void dump_common_audit_data(struct audit_buffer *ab,
 */
BUILD_BUG_ON(sizeof(a->u) > sizeof(void *)*2);
 
-   audit_log_format(ab, " pid=%d comm=", task_pid_nr(tsk));
-   audit_log_untrustedstring(ab, tsk->comm);
+   audit_log_format(ab, " pid=%d comm=", task_pid_nr(current));
+   audit_log_untrustedstring(ab, memcpy(comm, current->comm, 
sizeof(comm)));
 
switch (a->type) {
case LSM_AUDIT_DATA_NONE:
@@ -276,16 +276,19 @@ static void dump_common_audit_data(struct audit_buffer 
*ab,
audit_log_format(ab, " ino=%lu", inode->i_ino);
break;
}
-   case LSM_AUDIT_DATA_TASK:
-   tsk = a->u.tsk;
+   case LSM_AUDIT_DATA_TASK: {
+   struct task_struct *tsk = a->u.tsk;
if (tsk) {
pid_t pid = task_pid_nr(tsk);
if (pid) {
+   char comm[sizeof(tsk->comm)];
audit_log_format(ab, " pid=%d comm=", pid);
-   audit_log_untrustedstring(ab, tsk->comm);
+   audit_log_untrustedstring(ab,
+   memcpy(comm, tsk->comm, sizeof(comm)));
}
}
break;
+   }
case LSM_AUDIT_DATA_NET:
if (a->u.net->sk) {
struct sock *sk = a->u.net->sk;
-- 
1.7.1

--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit


Re: Suppress or exclude messages from /var/log/audit.log via audit.rules

2015-04-14 Thread [Cloud ASIA] Toshihiro Takehara
Dear Steve

Thank you very much for a lot of suggestions.
I apology for late response.

The messages you gave me was helpful, so I was able to resolve the problems.

Best Regards,
Toshihiro Takehara

=
Cloud ASIA Co., Ltd. [ 株式会社クラウドエイジア ]
Founder & CEO Takehara Toshihiro

  〒174-0073
  33-14-101, Higashiyama-cho, Itabashi-ku, Tokyo, Japan
  TEL: +81-3-6869-2994  FAX: +81-3-6869-3974
  Mobile: +81-90-4737-8137
  Mobile in Laos: +856-20-5912-2188
  http://www.cloud-asia.co.jp
  http://www.facebook.com/cloud.asia.japan
  takeh...@cloud-asia.co.jp

Lao Systems [ ラオシステムズ ]
  Founder & CEO Takehara Toshihiro
  http://lao-systems.jp/
=
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit