A penetration tester has identified several newly released CVEs on a VoIP call manager. The scanning tool the tester used determined the possible presence of the CVEs based off the version number of…

Question

Options

• AManually check the version number of the VoIP service against the CVE release
• BTest with proof-of-concept code from an exploit database
• CReview SIP traffic from an on-path position to look for indicators of compromise
• DUtilize an nmap -sV scan against the service

• A
  10% (4)
• B
  83% (34)
• C
  5% (2)
• D
  2% (1)

Explanation

The scanner identified potential CVEs solely based on the service version number - this is passive, fingerprint-based detection that generates possible findings, not confirmed vulnerabilities. To validate whether the vulnerability actually exists and is exploitable on this specific target, the best method is to test using proof-of-concept (PoC) exploit code from a database such as Exploit-DB. This actively confirms whether the CVE is exploitable against the target, distinguishing true positives from false positives. Option A (manually checking the version number) repeats what the scanner already did and adds no validation value. Option C (reviewing SIP traffic for IoC) looks for evidence of prior exploitation, not for whether the vulnerability exists. Option D (nmap -sV) performs version detection again - the same underlying method the original scanner used - and does not confirm exploitability.

No community discussion yet for this question.