Designate DNS – it’s possible to create blacklist using invalid patterns
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Scenario:
Create blacklist using string that cannot be used either as a regex or as a zone name, for example:
patterns = ['', '#(*&^%$%$#@$']
Empty pattern console result:
2021-07-01 10:36:29,649 770881 INFO [tempest.
2021-07-01 10:36:29,650 770881 DEBUG [tempest.
Body: {"pattern": "", "description": "tempest-
Response - Headers: {'date': 'Thu, 01 Jul 2021 07:36:29 GMT', 'server': 'Apache/2.4.41 (Ubuntu)', 'location': 'http://
Body: b'{"id": "81759d14-
}}}
Invalid string (#(*&^%$%$#@$") console result:
2021-07-01 10:32:32,316 770535 INFO [tempest.
2021-07-01 10:32:32,317 770535 DEBUG [tempest.
Body: {"pattern": "#(*&^%$%$#@$", "description": "tempest-
Response - Headers: {'date': 'Thu, 01 Jul 2021 07:32:32 GMT', 'server': 'Apache/2.4.41 (Ubuntu)', 'location': 'http://
Body: b'{"id": "4527e92e-
Actual Result:
Blacklist is successfully created
Expected result:
400 BadRequest
Changed in designate: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. opendev. org/c/openstack /designate/ +/825682
Review: https:/