Traceback

I’ve gotten too the part where you move into the folder but I get this error when in the machine. I reset it and got it again can someone help ?

Welcome to the Luvit repl!

Uncaught exception:

[string “bundle:deps/readline.lua”]:485: attempt to call method ‘set_mode’ (a nil value)
stack traceback:
[string “bundle:deps/readline.lua”]:485: in function ‘readLine’
[string “bundle:deps/repl.lua”]:198: in function ‘start’
[string “bundle:main.lua”]:137: in function ‘main’
[string “bundle:init.lua”]:49: in function <[string “bundle:init.lua”]:47>
[C]: in function ‘xpcall’
[string “bundle:init.lua”]:47: in function ‘fn’
[string “bundle:deps/require.lua”]:310: in function <[string “bundle:deps/require.lua”]:266>

so did someone break the machine as this happens between resets or is this an intended thing ? it seems like its having issues with the program it self and loading the needed functions ?

@Jowens066 said:

I’ve gotten too the part where you move into the folder but I get this error when in the machine. I reset it and got it again can someone help ?

Welcome to the Luvit repl!

Uncaught exception:

[string “bundle:deps/readline.lua”]:485: attempt to call method ‘set_mode’ (a nil value)
stack traceback:
[string “bundle:deps/readline.lua”]:485: in function ‘readLine’
[string “bundle:deps/repl.lua”]:198: in function ‘start’
[string “bundle:main.lua”]:137: in function ‘main’
[string “bundle:init.lua”]:49: in function <[string “bundle:init.lua”]:47>
[C]: in function ‘xpcall’
[string “bundle:init.lua”]:47: in function ‘fn’
[string “bundle:deps/require.lua”]:310: in function <[string “bundle:deps/require.lua”]:266>

so did someone break the machine as this happens between resets or is this an intended thing ? it seems like its having issues with the program it self and loading the needed functions ?

Does this also happen, when you just load the repl, without any parameters?

This is my first box ever. It took me a few hours.

Once I became root, I used my root privileges to chattr +i all of the flags and the .bash_history of root and the other two accounts after clearing them. This way no bash history can be recorded, preventing it from giving away clues from other users. Only root will be able to delete critical files now. This could have been done “out of the box” by the author.

@Karatekid430 said:

This is my first box ever. It took me a few hours.

Once I became root, I used my root privileges to chattr +i all of the flags and the .bash_history of root and the other two accounts after clearing them. This way no bash history can be recorded, preventing it from giving away clues from other users. Only root will be able to delete critical files now.

Well, on your server and until it is reset, yes.

This could have been done “out of the box” by the author.

True - and certainly worth suggesting. I’ve found quite often Linux boxes desperately need the creator to make critical files immutable - OpenAdmin was a good example of this.

Finally able to get user and root flags, very fun an simple box.

Can anyone PM me how they managed to get a root shell? I wasn’t able to so I had to get the flag in a very dirty way.

Rooted, very straightforward box

Foothold: no actual vulnerability, just traceback with some osint

User and root basic enumeration will help, just try to know what the box is doing

Feel free to pm if you need any hint

Very easy machine. Easiest of the easy machines I have owned. User to root just took me 15-20 seconds! I don’t know if that was intended or not.

Foothold : comments and irrelevant words always lead you to something interesting.

User and Root are just very basic enumeration you do for linux.

Feel free to pm if you need any hint

My first non-walkthrough machine ever! I’m so happy :smile:
First i blocked myself by using php shell instead of planned backdoor route :trollface: (throwing logs under my feet)
Then i tried to get user by launching external script instead of using the compiler :trollface:
And at last i tried to use totally wrong scripts for reverse shell :trollface:
But in the end it all came through! Big thanks to the Author! I learned a lot today!

Rooted last night at like 2 AM

Honestly not my favorite box, requires a lot of guesswork. If you need nudges tho PM me.

Having a hard time getting my edit to appear in the writable file. If anyone has a nudge, I would appreciate it!

@xkcm said:

Having a hard time getting my edit to appear in the writable file. If anyone has a nudge, I would appreciate it!

Timing is key.

User done. That was fun :smile:

Type your comment> @hughesdg said:

User done. That was fun :smile:

I finally got into the box, but am stuck in W*******n. Have any nudges?

Type your comment> @TazWake said:

@xkcm said:

Having a hard time getting my edit to appear in the writable file. If anyone has a nudge, I would appreciate it!

Timing is key.

actually if you lgn while your rv is in it exct it and tada …

@MrRoxxx said:
Type your comment> @hughesdg said:

User done. That was fun :smile:

I finally got into the box, but am stuck in W*******n. Have any nudges?

what do we always try when we are inside the box?

Type your comment> @xkcm said:

Having a hard time getting my edit to appear in the writable file. If anyone has a nudge, I would appreciate it!

umm did you try to eco it out? … remember to use “>>” instead of “>”!

Spoiler Removed

can someone help?
after uploading the .l** scripts unable to execute them
the -e flag gives “[string “REPL”]:1: unexpected symbol near ‘/’”

Rooted at last. Timing is everything here!

anyone else having a hard time staying connected to this box?