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. |

| Subject: | Is this exploitable?.. |
|---|---|
| Date: | Wed, 15 Dec 2004 14:42:24 -0800 |
I was looking at the follong code in J2EE 1.4.1 HttpServlet.java and it
looks like it may be possible to exploit it:
672 protected void doTrace(HttpServletRequest req,
HttpServletResponse resp)
673 throws ServletException, IOException
674 {
675
676 int responseLength;
677
678 String CRLF = "\r\n";
679 String responseString = "TRACE "+ req.getRequestURI()+
680 " " + req.getProtocol();
681
682 Enumeration reqHeaderEnum = req.getHeaderNames();
683
684 while( reqHeaderEnum.hasMoreElements() ) {
685 String headerName =
(String)reqHeaderEnum.nextElement();
686 responseString += CRLF + headerName + ": " +
687 req.getHeader(headerName);
688 }
689
690 responseString += CRLF;
691
692 responseLength = responseString.length();
693
694 resp.setContentType("message/http");
695 resp.setContentLength(responseLength);
696 ServletOutputStream out = resp.getOutputStream();
697 out.print(responseString);
698 out.close();
699 return;
700 }
It looks like responseString obtained from req is forgeable and this may
conceivably lead to a vulnerability down the line, it seems, when
responseString is output with a call to out.print(responseString).
Please advise.
-Ben
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Whitepaper "SESSION RIDING - A Widespread Vulnerability in Today's Web Applications", Thomas Schreiber |
|---|---|
| Next by Date: | RE: SQL injection (no single quotes used), Michael Howard |
| Previous by Thread: | Whitepaper "SESSION RIDING - A Widespread Vulnerability in Today's Web Applications", Thomas Schreiber |
| Next by Thread: | Re: Is this exploitable?.., Peter Conrad |
| Indexes: | [Date] [Thread] [Top] [All Lists] |