bryan rasmussen wrote:
http://metasploit.com/research/vulns/google_proxystylesheet/
A security hole in the google search appliance is xslt based,
basically from what I've seen of the appliance this is something that
an administrator should be able to fix themselves. But if one can't go
through all the configuration possibilities there is a patch.
I was not aware that the stylesheet engine was oracle based as is
indicated here though, one of the things that I had assumed from talks
with google support was that theirs was not a complete xslt 1.0
implementation - based on my asking for document function support and
being told that it supported all the functions that it needed to do
its job - which sounded like a no to me.
I wish we could discuss the google search appliance's XSL other than
generalities. I think it sucks. The XML is fine, though not very
descriptive. I don't understand why such a simple thing needs to be
secret. (Maybe because it is lame?) (Can I be sued for these statements?)
What I do (and it eliminates the bug) is use a servlet filter to get the
form submission, form a query to submit to the appliance and get the
results backs as XML to do with what I may.
best,
-Rob
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--