From: Eric Paris <eparis@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: nikola.ciprich@linuxbox.cz, linux-audit@redhat.com
Subject: Re: strange arguments in some EXEC audit events
Date: Mon, 02 Mar 2009 09:48:19 -0500 [thread overview]
Message-ID: <1236005299.5466.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20090302141744.GA31524@develbox.linuxbox.cz>
On Mon, 2009-03-02 at 15:17 +0100, Nikola Ciprich wrote:
> Hello,
> I'd like to ask about one thing regarding audit I don't understand:
> We are running auditd configured to log some syscalls (ie exec) and everything works fine, but quite often we're getting
> some strange records:
> type=SYSCALL msg=audit(1236001721.608:55239): arch=c000003e syscall=59 success=yes exit=0 a0=7f1407a74653 a1=7fff1088d710 a2=12cf580 a3=7f1408884770 items=2 ppid=20278 pid=23246 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts4 ses=25 comm="sh" exe="/bin/bash" subj=kernel key=(null)
> type=EXECVE msg=audit(1236001721.608:55239): argc=3 a0="sh" a1="-c" a2=66696C65202D4C202F7661722F6C6F672F61756469742F61756469742E6C6F6720323E2F6465762F6E756C6C
> type=CWD msg=audit(1236001721.608:55239): cwd="/var/log/audit"
> type=PATH msg=audit(1236001721.608:55239): item=0 name="/bin/sh" inode=97403 dev=08:01 mode=0100755 ouid=0 ogid=0 rdev=00:00 obj=unlabeled
> type=PATH msg=audit(1236001721.608:55239): item=1 name=(null) inode=63681 dev=08:01 mode=0100755 ouid=0 ogid=0 rdev=00:00 obj=unlabeled
> type=SYSCALL msg=audit(1236001721.609:55240): arch=c000003e syscall=59 success=yes exit=0 a0=11ee410 a1=11ee9d0 a2=11ed260 a3=0 items=2 ppid=23246 pid=23247 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts4 ses=25 comm="file" exe="/usr/bin/file" subj=kernel key=(null)
>
> I'm not sure what "66696C65202D4C202F7661722F6C6F672F61756469742F61756469742E6C6F6720323E2F6465762F6E756C6C" argument might be, is it somehow encoded string? It seems to remain unchanged across multiple events...
> Could somebody shed some light on it for me?
> Thanks a lot in advance!
It's a hex representation of the actual bits sent to audit. In this
case it is a string which contains the space character. Since we don't
really trust use strings when they contain non-letters we encode it like
this. This translates to "file -L /var/log/audit/audit.log 2>/dev/null"
http://www.dolcevie.com/js/converter.html does a nice easy conversion...
next prev parent reply other threads:[~2009-03-02 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 14:17 strange arguments in some EXEC audit events Nikola Ciprich
2009-03-02 14:48 ` Eric Paris [this message]
2009-03-02 15:15 ` Steve Grubb
2009-03-02 17:43 ` Nikola Ciprich
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=1236005299.5466.7.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=extmaillist@linuxbox.cz \
--cc=linux-audit@redhat.com \
--cc=nikola.ciprich@linuxbox.cz \
/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.