PT0-001 · Question #143
A vulnerability scan identifies that an SSL certificate does not match the hostname; however, the client disputes the finding. Which of the following techniques can the penetration tester perform to…
The correct answer is A. Ensure the scanner can make outbound DNS requests. SSL hostname mismatch validation requires the scanner to perform DNS resolution, so confirming outbound DNS is allowed is the correct way to adjudicate the finding.
Question
A vulnerability scan identifies that an SSL certificate does not match the hostname; however, the client disputes the finding. Which of the following techniques can the penetration tester perform to adjudicate the validity of the findings?
Options
- AEnsure the scanner can make outbound DNS requests.
- BEnsure the scanner is configured to perform ARP resolution.
- CEnsure the scanner is configured to analyze IP hosts.
- DEnsure the scanner has the proper plug -ins loaded.
How the community answered
(19 responses)- A79% (15)
- B5% (1)
- C5% (1)
- D11% (2)
Why each option
SSL hostname mismatch validation requires the scanner to perform DNS resolution, so confirming outbound DNS is allowed is the correct way to adjudicate the finding.
When a vulnerability scanner checks whether an SSL certificate's Common Name or Subject Alternative Names match the target hostname, it performs a DNS lookup to resolve the hostname and compare it against the certificate fields. If outbound DNS requests are blocked or misconfigured, the scanner cannot resolve hostnames correctly, which can produce false positives or false negatives on hostname mismatch findings - confirming DNS is reachable validates the result.
ARP resolution operates at Layer 2 to resolve IP addresses to MAC addresses on a local network segment and has no bearing on SSL certificate hostname matching.
Configuring the scanner to analyze IP hosts relates to how targets are enumerated by IP, not to validating DNS-based hostname fields embedded in SSL certificates.
While scanner plug-ins enable specific checks, the root cause of a disputed hostname mismatch finding is DNS resolution capability, not missing plug-ins.
Concept tested: DNS resolution dependency for SSL hostname mismatch validation
Source: https://docs.tenable.com/nessus/Content/DNSResolution.htm
Topics
Community Discussion
No community discussion yet for this question.