dns: prevent creation of cross-tenant conflicting DNS zones in the same server - #13946
dns: prevent creation of cross-tenant conflicting DNS zones in the same server#13946winterhazel wants to merge 2 commits into
Conversation
|
@blueorangutan package |
|
lgtm |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #13946 +/- ##
=========================================
Coverage 19.72% 19.73%
- Complexity 19944 19951 +7
=========================================
Files 6371 6371
Lines 575738 575765 +27
Branches 70471 70478 +7
=========================================
+ Hits 113587 113614 +27
+ Misses 449805 449798 -7
- Partials 12346 12353 +7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
@blueorangutan package |
|
@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18952 |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-16802)
|
Description
allocateDnsZoneallows users to register DNS zones that conflict with DNS zones from the same server belonging to other users, which consequently allows them to shadow DNS records belonging to other users.Example: Victim tenant runs
tenant1.cloud.examplewith www → 203.0.113.10 on a shared public server (suffixcloud.example). A co-tenant callscreateDnsZone name=www.tenant1.cloud.example dnsserverid=<shared>— accepted as-is — then adds an apex A record to their own IP; every resolver using that PowerDNS now resolves the victim's hostname to the attacker.This patch rejects zones that overlap another tenant's zone as either a DNS parent or child, and also requires a non-blank
publicDomainSuffixfor public servers. It was mostly generated using AI tools, but reviewed and tested by a human.Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
I reproduced the example scenario before the patch, and verified that it is not reproducible anymore after the changes.