CCE-90772-5Platform: rhel7 | Date: (C)2017-06-29 (M)2022-10-10 |
Disable Dynamic Updates
Is there a mission-critical reason to enable the risky dynamic
update functionality? If not, edit '/etc/named.conf'. For each zone
specification, correct the following directive if necessary:
zone "example.com " IN {
allow-update { none; };
...
};
Parameter:
Technical Mechanism:
Dynamic updates allow remote servers to add, delete, or modify any
entries in your zone file. Therefore, they should be considered highly risky,
and disabled unless there is a very good reason for their use. If dynamic
updates must be allowed, IP-based ACLs are insufficient protection, since they
are easily spoofed. Instead, use TSIG keys (see the previous section for an
example), and consider using the update-policy directive to restrict changes to
only the precise type of change needed.
Fix:
No Remediation Info
CCSS Severity: | CCSS Metrics: |
CCSS Score : | Attack Vector: |
Exploit Score: | Attack Complexity: |
Impact Score: | Privileges Required: |
Severity: | User Interaction: |
Vector: | Scope: |
| Confidentiality: |
| Integrity: |
| Availability: |
| |
References: