Official Spectra Discussion

I really enjoyed this box.

Big thanks to Galapag0s for the nudges!

Phew, spent way too many hours on foothold. Rest of the box is pretty straightforward from there. Overall this machine was a good lesson in taking a look at what you have before resorting to tools.

Thanks to Galapag0s as well for a nudge!

hi im new here if can someon show me how to start with hacking

Type your comment> @GHOSTanonymus said:

hi im new here if can someon show me how to start with hacking

Welcome to HTB. I great place to start is with the retired machines. Ippsec (find him on youtube) has some amazing walk throughs of the retired machines. Thats how I got started.

@Thanks bro but i dont have premiume so i cant do retired machines

The last two are available and there are still starting point & academy labs you can do without it costing money.

Its also worth watching the Ippsec videos even if you cant follow along.

However, this isn’t really related to the box so please start a new thread if you want to discuss this.

ou bro i think its cus i didnt select openvpn on port tcp 443

@GHOSTanonymus said:

ou bro i think its cus i didnt select openvpn on port tcp 443

It is still easier if you start a new thread or ask this in the threads already open for the machine you are working on, where other people can answer.

Not sure what you mean about selecting openvpn on port tcp 443 though. That isn’t really how it works.

idk how to start new thread bro pls give me some contact to contact u

@GHOSTanonymus said:

idk how to start new thread bro pls give me some contact to contact u

On the main page on the bottom right is a button you can use to create a new discussion.

You can message me on this. If you want to send a direct message, click on my name and send me a message. I am not sure how contacting me in different ways from asking questions on the forum will help though.

Fun box. Managed to root without any enum tool which is a first for me.

Struggled a bit to get user, but root was a complete piece of cake (<60sec); I’m curious if there was any other way with the n**e.*s stuff on the box?

Hi, may I message someone for some help on the initial foothold? Have found something but stumped on where to go from there.

Foothold: The usual web pentesting tools will basically point out anything you need. But the info is also pretty obvious. The way to get a shell is very generic and well documented in countless articles.

User: Really a lot of stuff to look through. Yes, you can run scripts if you play around a bit and some of them might help a bit. It’s a bit of a paperchase unless you just stumble on it by accident.

Root: Very basic enum and then google what you found

Rooted - thanks for the fun box.

Took me way longer than I care to admit to find the info I needed for user.

Type your comment> @sicario1337 said:

Type your comment> @baegmon said:

Is the box glitched for anyone else? I have root but I can’t see anything in the root directory even after a reset.

Thats probably because you are in the docker as root and not the host… try running “hostname” to confirm…

Definitely wasn’t the problem, tried it again after a couple days later and this time root.txt was found… idk

I’m still having problems with this box… I’ve reset it a couple times, still the issue persists.

I logged into the website, and I’m trying to edit files to gain a shell, however, it will not let me update any php files, whether in the theme editor or if I try to edit plugins. I keep getting this error:

“Unable to communicate back with site to check for fatal errors, so the PHP change was reverted. You will need to upload your PHP file change by some other means, such as by using SFTP.”

My research has shown that the issue is usually caused by plugin conflicts, or editing other setup/config files… However I’ve not edited anything, and plugins are deactivated by default. I even had a friend start the box the same time I did, they rooted it, and I’m here stuck with errors. Super frustrating knowing what and how to do what I need to do, but not being able to because I don’t know how to get around this error. Never had an issue before when it comes to editing a WP file to gain shell access…

Any help would be appreciated…

Type your comment> @quantumtheory said:

snip

I too had issues with this step. I believe others have had luck with a Framework, but I found a pretty cool script on GitHub that made the plugin for me and spun up a multi-handler listener :slight_smile:

Type your comment> @quantumtheory said:

I’m still having problems with this box… I’ve reset it a couple times, still the issue persists.

I logged into the website, and I’m trying to edit files to gain a shell, however, it will not let me update any php files, whether in the theme editor or if I try to edit plugins. I keep getting this error:

“Unable to communicate back with site to check for fatal errors, so the PHP change was reverted. You will need to upload your PHP file change by some other means, such as by using SFTP.”

My research has shown that the issue is usually caused by plugin conflicts, or editing other setup/config files… However I’ve not edited anything, and plugins are deactivated by default. I even had a friend start the box the same time I did, they rooted it, and I’m here stuck with errors. Super frustrating knowing what and how to do what I need to do, but not being able to because I don’t know how to get around this error. Never had an issue before when it comes to editing a WP file to gain shell access…

Any help would be appreciated…

Find my post here , it has a hint on what you are struggling on :smile:
PM if it feels too cryptic

@baegmon said:
Type your comment> @sicario1337 said:

Type your comment> @baegmon said:

Is the box glitched for anyone else? I have root but I can’t see anything in the root directory even after a reset.

Thats probably because you are in the docker as root and not the host… try running “hostname” to confirm…

Definitely wasn’t the problem, tried it again after a couple days later and this time root.txt was found… idk

Strange … Glad it worked later :smile:

i ssh into the box as k*** with a found password, i got directly into root, my guess is that thats not the intented way, please dont break the machines too much :neutral: