Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

Re: GET in Access Log File

Subject: Re: GET in Access Log File
Date: Wed, 26 Oct 2005 18:15:17 +1300
Thank you, your diagnosis was spot on so although they are trying the
server is just dishing up the index page. Just as a bit of extra info
I'm using <LimitExcept> to control methods.

Many thanks for the help from all.


On Tue, 2005-10-25 at 09:53 -0500, S.A.B.R.O. Net Security wrote:
It appears someone is indeed attemping to use your server as an open 
proxy via the HTTP GET tunnel trick.

This is also common with POST, CONNECT, etc....scan your logs for these 
types of attempts as well.

What's interesting is even though they received a status code of 200 
(Success) in your examples, the two different sites they
attempted to access both returned 1302 bytes....maybe this is your 
server feeding them your index.html and not the external site's page?

Try using the following :

telnet <your server> 80
then type CONNECT some.site.com:80 HTTP/1.0<enter><enter>

If it returns anything other then your index.html or an error status try 
checking out the following :

Check out the Limit option in httpd.conf:

        <Limit GET POST>
                .
                .
                .
        </Limit>

The above, when placed within a <directory /path/to/directory>....
</directory> section,  will only allow GET and POST requests to that
directory and it's sub-directories. Anything else will give the 405(Method
Not Allowed)  response that you see for the CONNECT request.


(Portions snagged from other sources.....kudos to the original authors).

-- 
Tony Barry

No Bull Services
PO Box 51528
Pakuranga
Auckland

021 413642
09 5768552

http://www.NO-BULL.CO.NZ
*************************************************************************

This e-mail and any files transmitted with it are confidential and
intended solely for the use of the addressee/s.
If you have received this e-mail in error please notify the sender.

************************************************************************* 

<Prev in Thread] Current Thread [Next in Thread>