Added code to assign CPORT value to the parent scanner object

[bwatters-r7]

This fixes the bug reported in #7236

As it exists currently, the assigned CPORT value never gets passed to the parent scanner object. I imagine it was simply overlooked. This fix simply passes the value up the chain as it was supposed to do.

Verification

List the steps needed to make sure this thing works

• Start msfconsole
• use auxiliary/scanner/smb/smb_login
• set rhosts <some_ip>
• run
• Verify the module uses a random source port
• Start msfconsole
• use auxiliary/scanner/smb/smb_login
• `set rhosts <some_ip>'
• set CPORT <some_port>
• run
• Verify the module uses the assigned source port

My tests.......

CPORT OFF

bwatters@ubuntu:~/rapid7/metasploit-framework$ ./msfconsole -q
msf > use auxiliary/scanner/smb/smb_login 
msf auxiliary(smb_login) > set rhosts <win8x64_IP>
rhosts => <win8x64_IP>
msf auxiliary(smb_login) > run

[*] <win8x64_IP>:445    - SMB - Starting SMB login bruteforce
[*] <win8x64_IP>:445    - This system does not accept authentication with any credentials, proceeding with brute force
[*] Scanned 1 of 1 hosts (100% complete)
[*] Auxiliary module execution completed

CPORT ON:

bwatters@ubuntu:~/rapid7/metasploit-framework$ ./msfconsole -q
msf > use auxiliary/scanner/smb/smb_login 
msf auxiliary(smb_login) > set rhosts <win8x64_IP>
rhosts => <win8x64_IP>
msf auxiliary(smb_login) > set cport 54321
cport => 54321
msf auxiliary(smb_login) > run

[*] <win8x64_IP>:445    - SMB - Starting SMB login bruteforce
[*] <win8x64_IP>:445    - This system does not accept authentication with any credentials, proceeding with brute force
[*] Scanned 1 of 1 hosts (100% complete)
[*] Auxiliary module execution completed

[wvu]

Another solid fix, @bwatters-r7.

[wvu]

Release Notes

This fixes the CPORT source port option for auxiliary/scanner/smb/smb_login. Previously, the local_port option wasn't being passed to Metasploit::Framework::LoginScanner::SMB. This PR corrects that behavior.

[wvu]

@bwatters-r7: For next time: https://github.com/blog/1506-closing-issues-via-pull-requests. :)