Skip to contentSkip to conversation

Q on nonuniform "recvfrom" avc message

DISCUSSION Bill Laut 2 participants 3 messages Jul 8, 2003 SELinux security module

lore
Share & tools
lore

Bill Laut

author
#0 lore raw

First of all, thank you for the advice on my previous newbie question about the disappearing boot messages. I'm now going through to edit my policy files to resolve the AVC messages.

While reviewing the syslog output, I came across something else I was wondering if someone could please explain to me? I'm connecting through a DSL with dynamic IP, and accordingly the DHCP server is polling me every two hours to reconfirm my lease on the address. The incoming UDP packet is being silently logged and dropped by NetFilter, and in this case wouldn't matter because dhcpcd doesn't create a UDP socket on port 68 anyway.

Sporadically, I'm seeing an AVC message which suggests that kjournald is trying to receive the packet. Below is a snippet from my syslog:

Jul  7 21:57:26 vortex kernel: UDP_rules: IN=eth1 OUT=
   MAC=00:50:ba:5e:22:f7:00:02:3b:00:db:ee:08:00 SRC=209.244.127.6
   DST=4.46.245.145 LEN=339 TOS=0x00 PREC=0x00 TTL=249 ID=53845 DF
   PROTO=UDP SPT=67 DPT=68 LEN=319
Jul  7 23:57:26 vortex kernel: UDP_rules: IN=eth1 OUT=
   MAC=00:50:ba:5e:22:f7:00:02:3b:00:db:ee:08:00 SRC=209.244.127.6
   DST=4.46.245.145 LEN=339 TOS=0x00 PREC=0x00 TTL=249 ID=41215 DF 
   PROTO=UDP SPT=67 DPT=68 LEN=319
Jul  8 01:57:26 vortex kernel: avc:  denied  { recvfrom } for  pid=11
   comm=kjournald saddr=209.244.127.6 source=17664 daddr=4.46.245.145 dest=339
   netif=eth1 scontext=system_u:system_r:initrc_t
   tcontext=system_u:object_r:netmsg_eth1_t tclass=packet_socket
Jul  8 01:57:26 vortex kernel: UDP_rules: IN=eth1 OUT=
   MAC=00:50:ba:5e:22:f7:00:02:3b:00:db:ee:08:00 SRC=209.244.127.6
   DST=4.46.245.145 LEN=339 TOS=0x00 PREC=0x00 TTL=249 ID=28605 DF PROTO=UDP
   SPT=67 DPT=68 LEN=319
Jul  8 03:57:26 vortex kernel: UDP_rules: IN=eth1 OUT=
   MAC=00:50:ba:5e:22:f7:00:02:3b:00:db:ee:08:00 SRC=209.244.127.6
   DST=4.46.245.145 LEN=339 TOS=0x00 PREC=0x00 TTL=249 ID=15995 DF PROTO=UDP
   SPT=67 DPT=68 LEN=319

Why is SELinux reporting that kjournald is trying to receive this packet? Is it because the violation occured in the kernel while kjournald happened to be the currently executing process? Or is SELinux telling me that there's a possible Trojan/BO/whatever buried inside of kjournald?

So far, this has occured in only two processes: kjournald and klogd. That's what sent my antennae up.

Finally, what is the "source=" and "dest=" reporting? Are they supposed to be the source/destination port numbers? It appears that there might be an error as the dest= number appears to be the packet length.

Thank you in advance for your advice.

--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#1 lore raw
Quoted 8 lines · Bill Laut

Sporadically, I'm seeing an AVC message which suggests that kjournald is trying to receive the packet. Below is a snippet from my syslog:

Jul  8 01:57:26 vortex kernel: avc:  denied  { recvfrom } for  pid=11
   comm=kjournald saddr=209.244.127.6 source=17664 daddr=4.46.245.145 dest=339
   netif=eth1 scontext=system_u:system_r:initrc_t
   tcontext=system_u:object_r:netmsg_eth1_t tclass=packet_socket
Quoted 4 lines

Why is SELinux reporting that kjournald is trying to receive this packet? Is it because the violation occured in the kernel while kjournald happened to be the currently executing process? Or is SELinux telling me that there's a possible Trojan/BO/whatever buried inside of kjournald?

The former. The avc_audit code simply tests current and current->pid
and includes the corresponding process information in the audit message if they are non-zero. Not useful in the case of 'recvfrom' or other checks performed on network input processing.

Quoted 6 lines

So far, this has occured in only two processes: kjournald and klogd. That's what sent my antennae up.

Finally, what is the "source=" and "dest=" reporting? Are they supposed to be the source/destination port numbers? It appears that there might be an error as the dest= number appears to be the packet length.

Yes, they are supposed to be the port numbers. In this case, they would be extracted by avc_audit from skb->h.uh->source and skb->h.uh->dest. Not sure about the discrepancy that you are seeing.

Signature · 8 lines
Stephen Smalley <[email protected]>
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.
author
#2 lore raw
Quoted 9 lines · Stephen Smalley
Quoted 7 lines · Bill Laut

[...]

Why is SELinux reporting that kjournald is trying to receive this packet?
Is it because the violation occured in the kernel while kjournald
happened to be the currently executing process? Or is SELinux telling me that there's a possible Trojan/BO/whatever buried inside of kjournald?

Quoted 5 lines

The former. The avc_audit code simply tests current and current->pid
and includes the corresponding process information in the audit message if they are non-zero. Not useful in the case of 'recvfrom' or other checks performed on network input processing.

Upon reading your reply, it occured to me that one of my sentences could have been misunderstood. When I speculated "... that there's a possible Trojan/BO/whatever buried inside of kjournald," I did not mean to suggest that SELinux has NSA "spyware" buried in it. I was thinking of something else entirely unrelated to NSA while typing that sentence, and therefore didn't catch and filter out the inference before submitting the post.

To anyone at NSA who might have been offended at my sentence, I sincerely apologize for my faulty editing. From a security perspective, SELinux is, imho, the greatest thing since sliced bread and all of the Linux community owes NSA a debt of gratitude for having nurtured it into fruition.

Thanks again for all of your help.

--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.