Safe

Type your comment> @Z0d said:

For how long we should try to crack the hash of KP !! Running for ages with no luck, any suggestion.

I’m thinking of try to elevate to root using different approach if possible.

Got it!

If anyone has any hints on how to get to root, feel free to message me. I have all of the files. I have run j and H****** on the password file as well as steg bf to try and get the info out of the other files and can’t seem to get anywhere.

Guys any nudges on Binary exploitation of Safe- User? n00b BOF skills

Anyone willing to look over what I have been doing for BOF to give a hint where I might be going wrong for getting user.txt, been trying to get it to work for 6+ hours now…

How do you guys download the .k**x file from the system?

Type your comment> @FailWhale said:

How do you guys download the .k**x file from the system?

There is more than one way to connect to (and copy from) a machine. If you don’t know the password, but can write to the user’s directory, it’s usually quite possible to authorize your access another way.

@BT1483 right, I think I get you :slight_smile:

Spoiler Removed

It seems the address for the string I’d like to use for sm call to get a shell keeps changing (inside of lbc). Any tips on how to access that string during runtime? I can access the upe and execute it fine, since that addr doesn’t change, just the strings in l*bc keep moving around.

@Z0d said:
Type your comment> @azeroth said:

can anyone help me with master password for kee**** . i tried bruteforcing for hours but i didn’t get anything. please help me

When you extract the hash don’t forget the 6 files you have to add them, then the master key will be obtained quickly.

I only included one of the picture as the key file, is it the correct way?

Type your comment> @garnettk said:

@Z0d said:
Type your comment> @azeroth said:

can anyone help me with master password for kee**** . i tried bruteforcing for hours but i didn’t get anything. please help me

When you extract the hash don’t forget the 6 files you have to add them, then the master key will be obtained quickly.

I only included one of the picture as the key file, is it the correct way?

Each picture when extract with KP gave you a different hash.

Type your comment> @3lg470 said:

It seems the address for the string I’d like to use for sm call to get a shell keeps changing (inside of lbc). Any tips on how to access that string during runtime? I can access the upe and execute it fine, since that addr doesn’t change, just the strings in l*bc keep moving around.

Don’t try to guess the position of a string in a library the version of which you can’t even know (and hence also not where you find the string in it).

Type your comment> @BT1483 said:

Type your comment> @3lg470 said:

It seems the address for the string I’d like to use for sm call to get a shell keeps changing (inside of lbc). Any tips on how to access that string during runtime? I can access the upe and execute it fine, since that addr doesn’t change, just the strings in l*bc keep moving around.

Don’t try to guess the position of a string in a library the version of which you can’t even know (and hence also not where you find the string in it).

That actually makes a lot of sense, now that you say it, LOL. I did give up on that path. I was able to get what I need into another place (R9) but now trying to figure out how to get that into the s****m call. Of course, I also can put it all over the stack, but not sure how to get a pointer to one of those spots into RDI.

Is that more on the right track?

Type your comment> @3lg470 said:

That actually makes a lot of sense, now that you say it, LOL. I did give up on that path. I was able to get what I need into another place (R9) but now trying to figure out how to get that into the s****m call. Of course, I also can put it all over the stack, but not sure how to get a pointer to one of those spots into RDI.

Is that more on the right track?

Even though I don’t know where you got something into R9 (I took a different approach, apparently), and even though I don’t find a way to get it back out of there, I dare say the general idea is good.

Also, it might be a good idea to actually take a look at the disassembled code instead of just relying on tools to find gadgets.

You can of course also PM me if you don’t want to spam the boards.

I have did some enum en discovered the version of web server en also some stuff on a higher port. I have seen a lot of post here about some binary input but I really don’t have any idea what and how :frowning:

So please, can some one give me a nudge or send me a PM with some sites where i can read more about this technique?

Type your comment> @Z0d said:

Type your comment> @garnettk said:

@Z0d said:
Type your comment> @azeroth said:

can anyone help me with master password for kee**** . i tried bruteforcing for hours but i didn’t get anything. please help me

When you extract the hash don’t forget the 6 files you have to add them, then the master key will be obtained quickly.

I only included one of the picture as the key file, is it the correct way?

Each picture when extract with KP gave you a different hash.

the kp*$$2jo*n tool with switch -k would only allow one key file
or I should include all the picture file with the -k switch?
e.g. k
p*$$2jo*n -k 1.jpg 2.jpg 3.jpg MyP@sswd.kx

the kp*$$2jo*n tool with switch -k would only allow one key file
or I should include all the picture file with the -k switch?
e.g. k
p*$$2jo*n -k 1.jpg 2.jpg 3.jpg MyP@sswd.kx

Who said it is one line of command? maybe each picture needs to be run separately!

yes papa, eating sugar no papa… I was too ‘smart’ and miss almost everything, it was already right in the face. Don’t overthink it. :cheers: :smiley:

i want hint in rop with this machine plz

Type your comment> @elkomy said:

i want hint in rop with this machine plz

The binary here is actually a pretty good example of why you shouldn’t always rely on automated tools because they (usually) only think of one way to exploit a binary and might miss more “creative” ways. And it’s short enough that you can actually read the whole disassembly without getting bored.

Disassemble the code and take a look at the disassembly. A good disassembler will tell you what functions get called from what places and also what functions don’t get called.