Offshore :

Hi folks,
I´m stuck at offshore at the moment… I fully pwned admin.offshore.com and the next step ist MS02.client.offshore.com I think…

I think i found a vector, but I don´t have a clue how to exploit it… Maybe somone could help me with a little hint?

Would be much appreciated! :slight_smile:

Type your comment> @sigeri said:

im stuck on wsdl stuff any hint?

I had the same issue, but next day it worked…

Hi, I am working on OffShore and have gotten into dev.admin.offshore.com and currently stuck on GPLI. I have been able to get Admin access to the application, but struggling with getting the RCE and would appreciate getting a sanity check on how to proceed and if I am missing something obvious. Thanks.

Anyone able to provide a hint to NIX01 priv esc? I have been stuck on this for a few days now.

1 Like

Hello all,
PLS, can someone tell me what is the next target after NIX1? I really don’t know how to proceed…
Thanks

Hello,
is anyone working on this lab right now?
I would like to get some clues or answers to unlock me…
Thanks in advance.

Is it only me or Nix01 is very buggy? Seems can’t upload any file it just hangs on curl :thinking:

I’m having issue with psexec for 172.16.1.101

Traceback (most recent call last):
File “/usr/share/doc/python3-impacket/examples/psexec.py”, line 680, in
executer = PSEXEC(command, options.path, options.file, options.c, int(options.port), username, password, domain, options.hashes,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/share/doc/python3-impacket/examples/psexec.py”, line 85, in init
self.__lmhash, self.__nthash = hashes.split(‘:’)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: not enough values to unpack (expected 2, got 1)

This is also happening in the Parrot VM that HTB provides me.

Is this normal? There is NO Support from HTB
Error 500 from WEB-WIN01

Server Error in ‘/’ Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a “web.config” configuration file located in the root directory of the current web application. This tag should then have its “mode” attribute set to “Off”.

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the “defaultRedirect” attribute of the application’s configuration tag to point to a custom error page URL.