From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: 859120-forwarded@bugs.debian.org, cgzones <cgzones@googlemail.com>
Subject: Re: Bug#859120: ausearch -i segfault
Date: Thu, 30 Mar 2017 13:16:46 -0400 [thread overview]
Message-ID: <31726054.vLjpktXK65@x2> (raw)
In-Reply-To: <c1e4b71b-27fc-4399-d671-da156beac6fa@debian.org>
Hello,
On Thursday, March 30, 2017 12:27:29 PM EDT Laurent Bigonville wrote:
> Le 30/03/17 à 15:56, cgzones a écrit :
> I just received the following bug in debian:
> > ausearch segfaults on the following input in interpret mode:
> >
> > /sbin/ausearch -i --input file
> >
> > type=AVC msg=audit(1490829425.686:121): avc: denied { bind } for
> > pid=1034 comm="darkstat" scontext=system_u:system_r:darkstat_t:s0
> > tcontext=system_u:system_r:darkstat_t:s0 tclass=packet_socket
> > permissive=0
> > type=SYSCALL msg=audit(1490829425.686:121): arch=c000003e syscall=49
> > success=no exit=-13 a0=3 a1=7ffce52e04b0 a2=14 a3=373 items=0
> > ppid=1033 pid=1034 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0
> > egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="darkstat"
> > exe="/usr/sbin/darkstat" subj=system_u:system_r:darkstat_t:s0
> > key=(null)
> > type=SOCKADDR msg=audit(1490829425.686:121):
> > saddr=1100000302000000000000000000000000000000
> > type=PROCTITLE msg=audit(1490829425.686:121):
> > proctitle=2F7573722F7362696E2F6461726B73746174002D6900656E70307333002D2D63
> > 68726F6F74002F7661722F6C69622F6461726B73746174002D2D70696466696C65002F7661
> > 722F72756E2F6461726B737461742E706964002D2D696D706F7274006461726B737461742E
> > 6462002D2D6578706F7274006461726B737461742E64
> The user is running version 2.6.7 (the version that will be shipped in
> the upcoming stable release).
I just committed the fix for this. You can find it is here:
https://github.com/linux-audit/audit-userspace/commit/f85cb62f10644e347c16541c8aa988219a3b3501
Thanks for reporting it.
-Steve
> I can actually reproduce the issue with the following one line:
>
> type=SOCKADDR msg=audit(1490829425.686:121):
> saddr=1100000302000000000000000000000000000000
>
> I got the following stacktrace:
>
> #0 strlen () at ../sysdeps/x86_64/strlen.S:106
> #1 0x00007ffff79a04da in auparse_do_interpretation (type=type@entry=9,
> id=id@entry=0x7fffffffde00) at ../../../auparse/interpret.c:2917
> #2 0x000055555555d3f1 in interpret (rtype=1306, comma=0,
> val=0x555555771a93 "1100000302", '0' <repeats 30 times>, name=<optimized
> out>) at ../../../src/ausearch-report.c:359
> #3 output_interpreted_node (n=0x555555771bd0, e=e@entry=0x555555771ae8)
> at ../../../src/ausearch-report.c:296
> #4 0x000055555555d9e3 in output_interpreted (l=0x555555771ad0) at
> ../../../src/ausearch-report.c:151
> #5 output_record (l=0x555555771ad0) at ../../../src/ausearch-report.c:80
> #6 0x0000555555557cac in process_log_fd () at ../../../src/ausearch.c:445
> #7 0x000055555555782b in main (argc=4, argv=0x7fffffffe098) at
> ../../../src/ausearch.c:140
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2017-03-30 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ2a_Dc6nVRvcwgOe8j50vC=XxWjptPyNdH8noVZkU5hY0_wvg@mail.gmail.com>
2017-03-30 16:27 ` Bug#859120: ausearch -i segfault Laurent Bigonville
2017-03-30 17:16 ` Steve Grubb [this message]
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=31726054.vLjpktXK65@x2 \
--to=sgrubb@redhat.com \
--cc=859120-forwarded@bugs.debian.org \
--cc=cgzones@googlemail.com \
--cc=linux-audit@redhat.com \
/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.