/0 subnet causes dhcp failures
Bug #1362651 reported by
Salvatore Orlando
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Security Advisory |
Won't Fix
|
Undecided
|
Unassigned | ||
neutron |
Fix Released
|
High
|
Salvatore Orlando |
Bug Description
Neutron allow for creating /0 subnet. This alone does not make a lot of sense.
It also causes DHCP failures as the agent is not able to start the dnsmasq process.
Trouble is that the DHCP agent goes into perennial fully resync mode.
This might cause huge delays in setting up DHCP for other subnets, thus resulting in a potential DoS.
So it might be better to prevent /0 subnets at all.
information type: | Private Security → Public Security |
Changed in neutron: | |
milestone: | juno-3 → juno-rc1 |
Changed in ossa: | |
status: | Incomplete → Won't Fix |
tags: | added: havana-backport-potential icehouse-backport-potential |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
The OSSA tasks is set to incomplete pending additional review on this issue.
It looks related to https:/ /bugs.launchpad .net/ossa/ +bug/1333134... So if the "perennial fully resync mode" is effective, then we should confirm the OSSA task.