-
Notifications
You must be signed in to change notification settings - Fork 14.6k
Support Encrypted MSSQL Sessions #20677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
zeroSteiner
wants to merge
7
commits into
rapid7:master
Choose a base branch
from
zeroSteiner:fix/issue/18745
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+136
−209
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
ae05a12
Don't open pass_file if it's blank
zeroSteiner 85c6846
Use the new #starttls method
zeroSteiner f3eeb59
Switch to the new fiber relay manager
zeroSteiner 5c95aa6
Add the new encrypted MsTds channel
zeroSteiner 9a605e5
Initialize the info for web sockets
zeroSteiner 9d00c08
Remove the old MS-TDS SSL Proxy code
zeroSteiner 750e664
Fix the PostreSQL SSL tests for #starttls method
zeroSteiner File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,62 @@ | ||
| # -*- coding: binary -*- | ||
|
|
||
| require 'bindata' | ||
|
|
||
| module Rex::Proto::MsTds | ||
| class Channel | ||
| include Rex::IO::StreamAbstraction | ||
|
|
||
| attr_reader :params | ||
|
|
||
| # the socket that makes the outbound connection to the SQL server | ||
| attr_reader :sock | ||
|
|
||
| def initialize(opts = {}) | ||
| @params = Rex::Socket::Parameters.from_hash(opts) | ||
|
|
||
| # it doesn't work this way so throw an exception so that's clear | ||
| raise RuntimeError.new('SSL incompatible with MsTds::Socket') if @params.ssl | ||
| raise ArgumentError.new('MsTds::Socket must be TCP') if @params.proto != 'tcp' | ||
|
|
||
| @sock = Rex::Socket.create_param(@params) | ||
| initialize_abstraction | ||
|
|
||
| lsock.initinfo(@sock.peerinfo, @sock.localinfo) | ||
|
|
||
| monitor_sock(@sock, sink: method(:_read_handler), name: 'MonitorLocal', on_exit: method(:_exit_handler)) | ||
| end | ||
|
|
||
| def write(buf, opts = {}) | ||
| if negotiating_ssl? | ||
| Rex::IO::RelayManager.io_write_all(self.sock, [18, 0x01, buf.length + 8, 0x0000, 0x00, 0x00].pack('CCnnCC') + buf) - 8 | ||
| else | ||
| Rex::IO::RelayManager.io_write_all(self.sock, buf) | ||
| end | ||
| end | ||
|
|
||
| def starttls | ||
| self.lsock.starttls(params) | ||
| end | ||
|
|
||
| protected | ||
|
|
||
| def negotiating_ssl? | ||
| return false unless self.lsock.is_a?(Rex::Socket::SslTcp) | ||
| return false if self.lsock.sslsock.state.start_with?('SSLOK') | ||
|
|
||
| true | ||
| end | ||
|
|
||
| def _exit_handler | ||
| self.rsock.close | ||
| end | ||
|
|
||
| def _read_handler(buf) | ||
| if negotiating_ssl? | ||
| Rex::IO::RelayManager.io_write_all(self.rsock, buf[8..]) + 8 | ||
| else | ||
| Rex::IO::RelayManager.io_write_all(self.rsock, buf) | ||
| end | ||
| end | ||
| end | ||
| end |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was removed because the
#closemethod is no longer replaced with something that'd close the channel. The original logic was prone to creating recursion loops during development and would send a close command back to Meterpreter when Meterpreter initiated the close operation.The new implementation should simply things by always closing the channel from the channel object level instead of the
rsock. Now when a channel is closed by Meterpreter, the#dio_close_handlerwill simply close and cleanup the channel locally without echoing the command back to Meterpreter.When the channel is closed by Metasploit Framework, it's either closed by
lsock.closewhich causes an EOF to be read in the Relay Manager which will dispatch to theon_exitcallback, which by default calls#close_write. Alternatively, the channel object can be closed directly, but there's no longer a loop as everything is notified.