>Number: 4226
>Category: mod_jserv
>Synopsis: The ServerSocket is binding to IN_ADDR_ANY
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: jserv
>State: open
>Class: support
>Submitter-Id: apache
>Arrival-Date: Sun Apr 11 17:00:01 PDT 1999
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.0b3
>Environment:
ALL
>Description:
The ServerSocket is binding to IN_ADDR_ANY which is a potential performance
issue, but more importantly exposes the servlet engine to the outside world,
DoS attacks are way to simple here.
>How-To-Repeat:
>Fix:
This can easily be rectified in
src/java/org/apache/java/net/AuthenticatedServerSocket.java when the call to
the superclass's constructor occurs. As in interim fix, I set mine to bind
only to 127.0.0.1 or InetAddress.getByName("localhost") as the third parameter.
As a long term fix I think the jserv.properties should contain not only a port
directive but an address/port pair similar to the Listen directive in Apache
would be nice. I would like to help with this effort on other fronts if any is
needed please get in touch.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request ]
[from a developer. ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]
