mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Fwd: [PATCH] Audit: fix handling of 'strings' with NULL characters
       [not found] <1542533951.1702681237470446245.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
@ 2009-03-19 13:48 ` Miloslav Trmac
  0 siblings, 0 replies; only message in thread
From: Miloslav Trmac @ 2009-03-19 13:48 UTC (permalink / raw)
  To: viro; +Cc: akpm, Steve Grubb, John Dennis, linux-kernel, Eric Paris

[-- Attachment #1: Type: text/plain, Size: 60 bytes --]

Hello,
this appears to have been lost somewhere...
    Mirek

[-- Attachment #2: Type: message/rfc822, Size: 3545 bytes --]

From: Eric Paris <eparis@redhat.com>
To: linux-audit@redhat.com, linux-kernel@vger.kernel.org
Cc: viro@zeniv.linux.org.uk, jdennis@redhat.com, mitr@redhat.com, akpm@linux-foundation.org, sgrubb@redhat.com
Subject: [PATCH] Audit: fix handling of 'strings' with NULL characters
Date: Thu, 11 Sep 2008 17:48:39 -0400
Message-ID: <1221169719.2952.14.camel@localhost.localdomain>

currently audit_log_n_untrustedstring() uses
audit_string_contains_control() to check if the 'string' has any control
characters.  If the 'string' has an embedded NULL
audit_string_contains_control() will return that the data has no control
characters and will then pass the string to audit_log_n_string with the
total length, not the length up to the first NULL.  audit_log_n_string
does a memcpy of the entire length and so the actual audit record
emitted may then contain a NULL and then whatever random memory is after
the NULL.

Since we want to log the entire octet stream (if we can't trust the data
to be a string we can't trust that a NULL isn't actually a part of it)
we should just consider NULL as a control character.  If the caller is
certain they want to stop at the first NULL they should be using
audit_log_untrustedstring.

Signed-off-by: Eric Paris <eparis@redhat.com>

---

Miloslav, this is also going to take care of nulls in the TTY_AUDIT_USER
message from userspace.  Is it going to be common to have control
characters on that code path as well?  Do you want to change
audit_receive_msg() to also use the hex encoding directly instead of the
_n_untrustedstring interface?

 kernel/audit.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/kernel/audit.c b/kernel/audit.c
index 4414e93..ccb8d68 100644
--- a/kernel/audit.c
+++ b/kernel/audit.c
@@ -1370,7 +1370,7 @@ void audit_log_n_string(struct audit_buffer *ab, const char *string,
 int audit_string_contains_control(const char *string, size_t len)
 {
 	const unsigned char *p;
-	for (p = string; p < (const unsigned char *)string + len && *p; p++) {
+	for (p = string; p < (const unsigned char *)string + len; p++) {
 		if (*p == '"' || *p < 0x21 || *p > 0x7e)
 			return 1;
 	}



^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-03-19 13:49 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1542533951.1702681237470446245.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2009-03-19 13:48 ` Fwd: [PATCH] Audit: fix handling of 'strings' with NULL characters Miloslav Trmac

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome