|
|||||||||||
|
RE: [OWASP-VULNXML] Re: no standards for webapp exploitation
From: Dawes, Rogan (ZA - Johannesburg) <rdawes(at)deloitte.co.za>
Date: Thu Jul 03 2003 - 10:29:08 EDT
As far as VulnXML goes, the aim is to describe a vulnerability in the HTTP applications that are called by a particular URL. The intention is not to describe a vulnerability in the HTTP server itself, which goes outside of the protocol spec. I think that that sort of thing is well handled by tools such as Nessus (NASL), and quite likely your Canvas tool as well. Consequently, VulnXML is centered quite heavily around the protocol definition, and does not attempt to address the vulnerabilities outside the protocol. My prototype VulnXML for the the IIS Chunked Encoding Buffer overflow indicated that that was not a realistic goal for VulnXML :-) One real gap in VulnXML that I do see is as you describe, though: Support for concurrent requests, to test for inadequate application locking as illustrated in WebGoat. Maybe we need to think about how we can include that kind of description in VulnXML. Rogan > -----Original Message-----
Important Notice: This email is subject to important restrictions, qualifications and disclaimers ("the Disclaimer") that must be accessed and read by clicking here or by copying and pasting the following address into your Internet browser's address bar: http://www.Deloitte.co.za/Disc.htm. The Disclaimer is deemed to form part of the content of this email in terms of Section 11 of the Electronic Communications and Transactions Act, 25 of 2002. If you cannot access the Disclaimer, please obtain a copy thereof from us by sending an email to ClientServiceCentre(at)Deloitte.co.za. Received on Thu Jul 3 11:42:29 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:07:53 EDT |
||||||||||
|
|||||||||||