This security issue was reported by Jann Horn and has to do with a lack of netns ownership check in lxc-user-nic, which would allow any user with a lxc-usernet allocation to create network interfaces on the host including choosing the name of that network interface. The created interface wouldn't be UP so is unlikely to be automatically brought up or get an address, but this issue could be used to squat the name of a real system network interface before it appears.
This security issue was reported by Jann Horn and has to do with a lack of netns ownership check in lxc-user-nic, which would allow any user with a lxc-usernet allocation to create network interfaces on the host including choosing the name of that network interface. The created interface wouldn't be UP so is unlikely to be automatically brought up or get an address, but this issue could be used to squat the name of a real system network interface before it appears.
https://lists.linuxcontainers.org/pipermail/lxc-users/2017-March/012925.html
I labeled as content spoofing given that the renaming could be used to "spoof" actual services. Also, the fix seems to be to not let users rename interfaces. I have changed this issue to 'local'. I can't see why this should be 'remote' -- shibumi
Vulmon