yahoo-eng-team team mailing list archive

[OpenStack Infra <1902917@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/ossa/+/800107
Committed: https://opendev.org/openstack/ossa/commit/239ec3826a74c4f3ffb1239cc574f95c6097c631
Submitter: "Zuul (22348)"
Branch:    master

commit 239ec3826a74c4f3ffb1239cc574f95c6097c631
Author: Jeremy Stanley <fungi@xxxxxxxxxxx>
Date:   Thu Jul 8 20:49:35 2021 +0000

    Add OSSA-2021-001 (CVE-2021-20267)
    
    Change-Id: I6bcc8392831efbdc7759b0ed5340023bb0440c85
    Closes-Bug: #1902917


** Changed in: ossa
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1902917

Title:
  Anti-spoofing bypass using Open vSwitch (CVE-2021-20267)

Status in neutron:
  Fix Released
Status in OpenStack Security Advisory:
  Fix Released

Bug description:
  Using Open vSwitch on an ussuri setup with neutron 16.0.0, VMs can
  send ICMPv6 Neighbor Advertisement packets with no check on their
  content to mis-direct traffic to them.

  This looks a lot like https://bugs.launchpad.net/neutron/+bug/1502933
  except it affects Open vSwitch driver rather than iptables.

  Pre-condition:

  - two running VMs in the same L2 flat network with IPv6 connectivity

  How to reproduce:

  - manually add a custom IPv6 on one (e.g. `ip -6 address add fe80::42/64 dev eth0`)
  - ping it from the other, expecting no answer (e.g. `ping -c1 -w1 "fe80::42%eth0"`)
  - confirm it updated its neighbor table (e.g. `ip -6 neigh get fe80::42/64 dev eth0`)

  Expected behavior:

  - VMs should not be able to advertise IPv6 addresses that are not
  assigned to them e.g. through neighbor advertisement packets.

  Affected versions:

  The Openstack version I am using is Ussuri with neutron 16.0.0, with
  minor changes on commit df5b28c2e5. From a quick review of the diff
  with master, I think the issue is also present there. Network part is
  using Open vSwitch on flat network with Xen 4.13 as hypervisor.

  Similarly, UDP packets using DHCP query ports (for DHCP v4 or v6) can be sent with arbitrary IP and MAC addresses.
  And I think we are fine for other ICMP types (redirect, router renumbering for ICMPv6) as I did not managed to have such packets sent between VMs but I fail to understand how it gets filtered.

  I am attaching a couple patches that I think fix the issues but
  include no tests and include changes that we may want to avoid (in
  case plugins out of neutron git repo use
  firewall.ICMPV6_ALLOWED_EGRESS_TYPES).

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1902917/+subscriptions