Greetings!
"Apache Tomcat WebDav Remote Information Disclosure Vulnerability " was published on october 14, 2007. -- at milw0rm
The code worked fine for tomcats operationg over normal http. But while testing for my client's tomcat server, I noticed that something is missing.
I was trying to use the exploit code against a tomcat hosting a site over a secured channel. I was unable to get any result.
And I noticed that that 'something' was "support for tomcats operating over SSL".
Day before yesterday, I wrote the new code (obviousley referred the older code) with new way to create socket- to operate over ssl.
Tested against the tomcat under test, and crosschecked with wireshark. Appears to work fine and effectively.
"Apache Tomcat WebDav Remote Information Disclosure Vulnerability with support for https" was published on october 21, 2007. -- please checkout the links below.
--------------------------------
If one looks at the several results returned by google for the mentioned DoRk, addresses starting with plain 'http' are far more in number, as compared to addresses starting with 'https'. At the same time it's easily noticable that the servers running over ssl are intentionally secured, and are more important for some reason.
Why security is a primary concern for a few of them?
It's quite obvious that chances are more, for servers operating over a secured channel - are containing more sensitive stuff as compared to others(operating over plain http).
Hence testing these 'secured' targets becomes something that has probably more overall impact.
Links:
Apache Tomcat (webdav) Remote File Disclosure Exploit (ssl support)
Security focus
http://www.securityfocus.com/bid/26070/
All the best!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment