DNS available externally on provider network

[Ian Kumlien]

DNS is open for everyone on our external provider network and this can be used to do a amplification attack.

Shouldn't this access at least be filtered for external parties?

Tested on openstack pike

[Jeremy Stanley (fungi)]

Since this report concerns a possible security risk, an incomplete security advisory task has been added while the core security reviewers for the affected project or projects confirm the bug and discuss the scope of any vulnerability along with potential solutions.

[Jeremy Stanley (fungi)]

In keeping with recent OpenStack vulnerability management policy changes, no report should remain under private embargo for more than 90 days. Because this report predates the change in policy, the deadline for public disclosure is being set to 90 days from today. If the report is not resolved within the next 90 days, it will revert to our public workflow as of 2020-05-27. Please see http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012721.html for further details.

[Ian Kumlien (pomac)]

This bug should apparently be merged with https://bugs.launchpad.net/neutron/+bug/1501206

And it has been fixed since:
13.0.3 - rocky
12.0.6 - queens
11.0.7 - pike

Fixed in all newer releases.

[Jeremy Stanley (fungi)]

Thanks! I've switched this to public and marked it as a duplicate.