From: Jeffrey Vander Stoep <firstname.lastname@example.org> To: David Miller <email@example.com> Cc: firstname.lastname@example.org, LSM List <email@example.com>, firstname.lastname@example.org Subject: Re: [PATCH 1/2] rtnetlink: gate MAC address with an LSM hook Date: Fri, 23 Aug 2019 13:41:38 +0200 Message-ID: <CABXk95BF=RfqFSHU_---DRHDoKyFON5kS_vYJbc4ns2OSemail@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Fri, Aug 23, 2019 at 1:19 AM David Miller <email@example.com> wrote: > > From: Jeff Vander Stoep <firstname.lastname@example.org> > Date: Wed, 21 Aug 2019 15:45:47 +0200 > > > MAC addresses are often considered sensitive because they are > > usually unique and can be used to identify/track a device or > > user . > > > > The MAC address is accessible via the RTM_NEWLINK message type of a > > netlink route socket. Ideally we could grant/deny access to the > > MAC address on a case-by-case basis without blocking the entire > > RTM_NEWLINK message type which contains a lot of other useful > > information. This can be achieved using a new LSM hook on the netlink > > message receive path. Using this new hook, individual LSMs can select > > which processes are allowed access to the real MAC, otherwise a > > default value of zeros is returned. Offloading access control > > decisions like this to an LSM is convenient because it preserves the > > status quo for most Linux users while giving the various LSMs > > flexibility to make finer grained decisions on access to sensitive > > data based on policy. > > > >  https://adamdrake.com/mac-addresses-udids-and-privacy.html > >  Other access vectors like ioctl(SIOCGIFHWADDR) are already covered > > by existing LSM hooks. > > > > Signed-off-by: Jeff Vander Stoep <email@example.com> > > I'm sure the MAC address will escape into userspace via other means, > dumping pieces of networking config in other contexts, etc. I mean, > if I can get a link dump, I can dump the neighbor table as well. These are already gated by existing LSM hooks and capability checks. They are not allowed on mandatory access control systems unless explicitly granted. > > I kinda think this is all very silly whack-a-mole kind of stuff, to > be quite honest. We evaluated mechanisms for the MAC to reach unprivileged apps. A number of researchers have published on this as well such as: https://www.usenix.org/conference/usenixsecurity19/presentation/reardon Three "leaks" were identified, two have already been fixed. -ioctl(SIOCGIFHWADDR). Fixed using finer grained LSM checks on socket ioctls (similar to this change). -IPv6 IP addresses. Fixed by no longer including the MAC as part of the IP address. -RTM_NEWLINK netlink route messages. The last mole to be whacked. > > And like others have said, tomorrow you'll be like "oh crap, we should > block X too" and we'll get another hook, another config knob, another > rulset update, etc. This seems like an issue inherent with permissions/capabilities. I don’t think we should abandon the concept of permissions because someone can forget to add a check. Likewise, if someone adds new code to the kernel and omits a capable(CAP_NET_*) check, I would expect it to be fixed like any other bug without the idea of capability checks being tossed out. We need to do something because this information is being abused. Any recommendations? This seemed like the simplest approach, but I can definitely appreciate that it has downsides. I could make this really generic by adding a single hook to the end of sock_msgrecv() which would allow an LSM to modify the message to omit the MAC address and any other information that we deem as sensitive in the future. Basically what Casey was suggesting. Thoughts on that approach? Thanks for your help on this.
next prev parent reply index Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-21 13:45 Jeff Vander Stoep 2019-08-21 13:55 ` Jeffrey Vander Stoep 2019-08-21 14:34 ` Casey Schaufler 2019-08-21 14:52 ` Jeffrey Vander Stoep 2019-08-22 23:19 ` David Miller 2019-08-23 11:41 ` Jeffrey Vander Stoep [this message] 2019-08-23 21:41 ` David Miller 2019-08-27 20:47 ` Paul Moore 2019-08-29 7:45 ` Michal Kubecek 2019-08-30 21:46 ` Paul Moore 2019-08-23 4:24 ` kbuild test robot
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='CABXk95BF=RfqFSHU_---DRHDoKyFON5kS_vYJbc4ns2OSfirstname.lastname@example.org' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Linux-Security-Module Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-security-module/0 linux-security-module/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-security-module linux-security-module/ https://lore.kernel.org/linux-security-module \ firstname.lastname@example.org public-inbox-index linux-security-module Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-security-module AGPL code for this site: git clone https://public-inbox.org/public-inbox.git