lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <88e844b40908140812r17faaef7qcf145a329f0c48c8@mail.gmail.com>
Date: Fri, 14 Aug 2009 11:12:13 -0400
From: Guy <full-disclosure@...lamatix.com>
To: antoine@...to.fr, full-disclosure@...ts.grok.org.uk
Subject: Re: ByPass a BlueCoat Proxy 8100 Serie
	authentification

> ******************************************************************************************
> Test two : i just add a spoofed http header REFERER to a whitelisted (localdatabase) site
> Result   : W00t !!
> ******************************************************************************************

Can you elaborate on, "to a whitelisted (localdatabase) site"?

None of the rules defined in the Web Authentication Layer or Web
Access Layer have a "whitelist" attribute. In the list of available
actions for the Web Authentication Layer there's: "Do Not
Authenticate", "ForceAuthenticate1" and "Deny." In the Web Access
Layer list of available actions there are a couple dozen options, none
of which are labeled "whitelist" or "whitelisted."

Also, I'm not sure what you mean by "localdatabase". Internal http
traffic shouldn't hit the proxies...

Using an 8100-C with SG05 5.2.4.3.

-Guy

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ