i am still stuck on this The change you wanted was rejected. > > Maybe you tried to change something you didn’t have access to. …
does any one have any clue how to deal with it, I have reset the browser, the box, the pvn pack , I already have the user flag , while moving on to root I am stuck back at square one.
I got this after the box was reset and the account I created was deleted. creating a new one fixed it.
i am still stuck on this The change you wanted was rejected. > > Maybe you tried to change something you didn’t have access to. …
does any one have any clue how to deal with it, I have reset the browser, the box, the pvn pack , I already have the user flag , while moving on to root I am stuck back at square one.
I get that all the time.
Worked using Chromium and when I switched my own VM (kali VM)
You may have the right payload but it doesn’t work straight away as other payloads do. There’s caching involved, etc, so it might take a few more steps to actually trigger it.
The vuln can be hard to find. For what is worth, when a vulnerability has a CVE documented by NVD, it’ll show up after a search here: https://nvd.nist.gov/vuln/search - so worth a shot to see if there are potential candidates in there.
The usual 2cents:
Foothold/User: CVE has a PoC showing the way to generate a valid payload - look at the code to figure out where to use it
Root: while doing your usual check you’ll realize what this is about - and you’re a couple of commands from root
If anybody cared to set up the whole environment locally(like me), other payloads will not work locally. But everything works on the box. I was trying to reproduce everything locally but none other than “touch” seems to work. So do it directly on the box itself. Now I am trying for the root.
For the timing issue, i’d recommend that you use the mobile app version with time synced there. I couldn’t get anything on my machine to work, even with perfect synchronization.