When the internal webserver is enabled (default is disabled), an attacker might be able to trick an administrator logged to the dashboard into visiting a malicious website and extract information about the running configuration from the dashboard. The root cause of the issue is a misconfiguration of the Cross-Origin Resource Sharing (CORS) policy.
Weakness
The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Dnsdist | Powerdns | 1.9.0 (including) | 1.9.12 (excluding) |
| Dnsdist | Powerdns | 2.0.0 (including) | 2.0.3 (excluding) |
| Dnsdist | Ubuntu | esm-apps/xenial | * |
| Dnsdist | Ubuntu | upstream | * |
Extended Description
If a cross-domain policy file includes domains that should not be trusted, such as when using wildcards under a high-level domain, then the application could be attacked by these untrusted domains. In many cases, the attack can be launched without the victim even being aware of it.