Here. And here. Here too.
Just search exploit DB for local Linux exploits mentioning privilege escalation (or just privilege, like this search).
Capitalisation is important. It's the difference between "Helping your brother Jack off a horse" and "Helping your brother jack off a horse".
The Forum Rules, Forum FAQ and the BackTrack Wiki... learn them, love them, live them.
Not every exploit has to have shellcode, especially a local priv escalation one.
Tiocfaidh ár lá
When did I say that? The only place I can find in this thread where I even mentioned shellcode is in post 4 responding to the OP who was talking about seeing mostly shellcode in the local exploits he saw. In that post I only meant that IF the OP was actually looking at privilege escalation exploits that contained shellcode, there should be more to it than JUST shellcode.
The majority of Linux privilege escalation exploits I have seen have not used shellcode at all...
Capitalisation is important. It's the difference between "Helping your brother Jack off a horse" and "Helping your brother jack off a horse".
The Forum Rules, Forum FAQ and the BackTrack Wiki... learn them, love them, live them.
Capitalisation is important. It's the difference between "Helping your brother Jack off a horse" and "Helping your brother jack off a horse".
The Forum Rules, Forum FAQ and the BackTrack Wiki... learn them, love them, live them.
The exploit is always going to be a program, never just raw shellcode. The shellcode is merely a a string of pure machine code that performs a certain task (usually opens a shell, but can open calc.exe or anything).
With a privilege escalation exploit, you're going to download the exploit code, compile it, and then just ./exploit, and it'll either work or it won't.
The exploits listed are like the simplest exploits to run on exploit-db. you just compile and run them. you can use gcc. it takes 2 mins at the most. If the exploits dosent work then you dont have the vulnerable services that the exploit takes advantage of.
wh1t3 fang
If the target system doesn't have a compiler already installed (such as gcc, which is run from the command line btw) you can try compiling the exploit elsewhere and transferring it over in binary form. You need to make sure you compile the binary for the same architecture and platform as the target system though, so its generally better to compile on the target itself if a compiler is available.
Last edited by lupin; 01-28-2011 at 01:09 PM.
Capitalisation is important. It's the difference between "Helping your brother Jack off a horse" and "Helping your brother jack off a horse".
The Forum Rules, Forum FAQ and the BackTrack Wiki... learn them, love them, live them.