unixtcpip/hacking · Datasets at Hugging Face

text stringlengths 0 1.99k

[0] https://github.com/PenturaLabs/Linux_Exploit_Suggester
[1] https://code.google.com/p/unix-privesc-check/

finsupport was running the latest version of Debian with no local root exploits,
but unix-privesc-check returned:
WARNING: /etc/cron.hourly/mgmtlicensestatus is run by cron as root. The user
www-data can write to /etc/cron.hourly/mgmtlicensestatus
WARNING: /etc/cron.hourly/webalizer is run by cron as root. The user www-data
can write to /etc/cron.hourly/webalizer

so I add to /etc/cron.hourly/webalizer:
chown root:root /path/to/my_setuid_shell
chmod 04755 /path/to/my_setuid_shell

wait an hour, and ....nothing. Turns out that while the cron process is running
it doesn't seem to be actually running cron jobs. Looking in the webalizer
directory shows it didn't update stats the previous month. Apparently after
updating the timezone cron will sometimes run at the wrong time or sometimes not
run at all and you need to restart cron after changing the timezone. ls -l
/etc/localtime shows the timezone got updated June 6, the same time webalizer
stopped recording stats, so that's probably the issue. At any rate, the only
thing this server does is host the website, so I already have access to
everything interesting on it. Root wouldn't get much of anything new, so I move
on to the rest of the network.


--[ 6 ]-- Pivoting

The next step is to look around the local network of the box you hacked. This
is pretty much the same as the first Scanning & Exploiting step, except that
from behind the firewall many more interesting services will be exposed. A
tarball containing a statically linked copy of nmap and all its scripts that you
can upload and run on any box is very useful for this. The various nfs-* and
especially smb-* scripts nmap has will be extremely useful.

The only interesting thing I could get on finsupport's local network was another
webserver serving up a folder called 'qateam' containing their mobile malware.


--[ 7 ]-- Have Fun

Once you're in their networks, the real fun starts. Just use your imagination.
While I titled this a guide for wannabe whistleblowers, there's no reason to
limit yourself to leaking documents. My original plan was to:
1) Hack Gamma and obtain a copy of the FinSpy server software
2) Find vulnerabilities in FinSpy server.
3) Scan the internet for, and hack, all FinSpy C&C servers.
4) Identify the groups running them.
5) Use the C&C server to upload and run a program on all targets telling them
who was spying on them.
6) Use the C&C server to uninstall FinFisher on all targets.
7) Join the former C&C servers into a botnet to DDoS Gamma Group.

It was only after failing to fully hack Gamma and ending up with some
interesting documents but no copy of the FinSpy server software that I had to
make due with the far less lulzy backup plan of leaking their stuff while
mocking them on twitter.
Point your GPUs at FinSpy-PC+Mobile-2012-07-12-Final.zip and crack the password
already so I can move on to step 2!


--[ 8 ]-- Other Methods

The general method I outlined above of scan, find vulnerabilities, and exploit
is just one way to hack, probably better suited to those with a background in
programming. There's no one right way, and any method that works is as good as
any other. The other main ways that I'll state without going into detail are:

1) Exploits in web browers, java, flash, or microsoft office, combined with
emailing employees with a convincing message to get them to open the link or
attachment, or hacking a web site frequented by the employees and adding the
browser/java/flash exploit to that.
This is the method used by most of the government hacking groups, but you don't
need to be a government with millions to spend on 0day research or subscriptions
to FinSploit or VUPEN to pull it off. You can get a quality russian exploit kit
for a couple thousand, and rent access to one for much less. There's also
metasploit browser autopwn, but you'll probably have better luck with no
exploits and a fake flash updater prompt.

2) Taking advantage of the fact that people are nice, trusting, and helpful 95%
of the time.
The infosec industry invented a term to make this sound like some sort of
science: "Social Engineering". This is probably the way to go if you don't know
too much about computers, and it really is all it takes to be a successful
hacker [0].

[0] https://www.youtube.com/watch?v=DB6ywr9fngU


--[ 9 ]-- Resources

Links:

* https://www.pentesterlab.com/exercises/
* http://overthewire.org/wargames/
* http://www.hackthissite.org/
* http://smashthestack.org/
* http://www.win.tue.nl/~aeb/linux/hh/hh.html
* http://www.phrack.com/

[0] https://github.com/PenturaLabs/Linux_Exploit_Suggester

[1] https://code.google.com/p/unix-privesc-check/

finsupport was running the latest version of Debian with no local root exploits,

but unix-privesc-check returned:

WARNING: /etc/cron.hourly/mgmtlicensestatus is run by cron as root. The user

www-data can write to /etc/cron.hourly/mgmtlicensestatus

WARNING: /etc/cron.hourly/webalizer is run by cron as root. The user www-data

can write to /etc/cron.hourly/webalizer

so I add to /etc/cron.hourly/webalizer:

chown root:root /path/to/my_setuid_shell

chmod 04755 /path/to/my_setuid_shell

wait an hour, and ....nothing. Turns out that while the cron process is running

it doesn't seem to be actually running cron jobs. Looking in the webalizer

directory shows it didn't update stats the previous month. Apparently after

updating the timezone cron will sometimes run at the wrong time or sometimes not

run at all and you need to restart cron after changing the timezone. ls -l

/etc/localtime shows the timezone got updated June 6, the same time webalizer

stopped recording stats, so that's probably the issue. At any rate, the only

thing this server does is host the website, so I already have access to

everything interesting on it. Root wouldn't get much of anything new, so I move

on to the rest of the network.

--[ 6 ]-- Pivoting

The next step is to look around the local network of the box you hacked. This

is pretty much the same as the first Scanning & Exploiting step, except that

from behind the firewall many more interesting services will be exposed. A

tarball containing a statically linked copy of nmap and all its scripts that you

can upload and run on any box is very useful for this. The various nfs-* and

especially smb-* scripts nmap has will be extremely useful.

The only interesting thing I could get on finsupport's local network was another

webserver serving up a folder called 'qateam' containing their mobile malware.

--[ 7 ]-- Have Fun

Once you're in their networks, the real fun starts. Just use your imagination.

While I titled this a guide for wannabe whistleblowers, there's no reason to

limit yourself to leaking documents. My original plan was to:

1) Hack Gamma and obtain a copy of the FinSpy server software

2) Find vulnerabilities in FinSpy server.

3) Scan the internet for, and hack, all FinSpy C&C servers.

4) Identify the groups running them.

5) Use the C&C server to upload and run a program on all targets telling them

who was spying on them.

6) Use the C&C server to uninstall FinFisher on all targets.

7) Join the former C&C servers into a botnet to DDoS Gamma Group.

It was only after failing to fully hack Gamma and ending up with some

interesting documents but no copy of the FinSpy server software that I had to

make due with the far less lulzy backup plan of leaking their stuff while

mocking them on twitter.

Point your GPUs at FinSpy-PC+Mobile-2012-07-12-Final.zip and crack the password

already so I can move on to step 2!

--[ 8 ]-- Other Methods

The general method I outlined above of scan, find vulnerabilities, and exploit

is just one way to hack, probably better suited to those with a background in

programming. There's no one right way, and any method that works is as good as

any other. The other main ways that I'll state without going into detail are:

1) Exploits in web browers, java, flash, or microsoft office, combined with

emailing employees with a convincing message to get them to open the link or

attachment, or hacking a web site frequented by the employees and adding the

browser/java/flash exploit to that.

This is the method used by most of the government hacking groups, but you don't

need to be a government with millions to spend on 0day research or subscriptions

to FinSploit or VUPEN to pull it off. You can get a quality russian exploit kit

for a couple thousand, and rent access to one for much less. There's also

metasploit browser autopwn, but you'll probably have better luck with no

exploits and a fake flash updater prompt.

2) Taking advantage of the fact that people are nice, trusting, and helpful 95%

of the time.

The infosec industry invented a term to make this sound like some sort of

science: "Social Engineering". This is probably the way to go if you don't know

too much about computers, and it really is all it takes to be a successful

hacker [0].

[0] https://www.youtube.com/watch?v=DB6ywr9fngU

--[ 9 ]-- Resources

Links:

* https://www.pentesterlab.com/exercises/

* http://overthewire.org/wargames/

* http://www.hackthissite.org/

* http://smashthestack.org/

* http://www.win.tue.nl/~aeb/linux/hh/hh.html

* http://www.phrack.com/