axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: xml-axis/java/docs security.html
Date Fri, 07 Mar 2003 23:38:14 GMT
stevel      2003/03/07 15:38:14

  Modified:    java/docs security.html
  A completely bogus article on forced me to update the security document. 'SOAP cant
validate callers indeed'.
  Revision  Changes    Path
  1.3       +45 -6     xml-axis/java/docs/security.html
  Index: security.html
  RCS file: /home/cvs/xml-axis/java/docs/security.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- security.html	13 Jan 2003 21:41:38 -0000	1.2
  +++ security.html	7 Mar 2003 23:38:13 -0000	1.3
  @@ -46,6 +46,28 @@
   are safe unless the server (or its DNS address) have been subverted; the
   server is vulnerable, and does need to be secured. 
  +<a href="">
  +Bilal Siddiqui
  +</a> makes the claim that <i> 
  +SOAP cannot distinguish between sensitive and non-sensitive web services
  +and cannot perform user authentication, authorization, and access
  +Again, this is another example of excess panic, perhaps combined with a
  +lack of knowledge of how SOAP servers are implemented. 
  +You do not need to follow this author's advice and have
  +separate SOAP servers for every level of sensitivity, or XML and SOAP
  +aware firewalls, any more than you need separate Web Servers for
  +different users, or require HTTP aware routers to restrict parts of a
  +web server to different IP addresses. 
   <h2>Common Attack Types</h2>
  @@ -76,9 +98,10 @@
   processing incoming XML needs to know and resist these. 
  -<li>Large XML Docukents<br>. Have a client post an XML doc of
  +<li>Large XML Documents<br> 
  +Have a client post an XML doc of
   extreme length/depth
   This does bad things to DOM parsers and memory consumption on the
   server: a DoS attack. The issue here is that the costs of handling a
   large XML document are much greater than the cost of generating one. 
  @@ -142,6 +165,7 @@
   Axis does not (yet) support HTTP1.1 Digest Authentication; if it does get added
   it will be via the 
   <a href="">HttpClient</a>
   <h2>Securing your Services</h2>
  @@ -201,15 +225,17 @@
   expression expected, and check its length. Better yet apply any other
   higher level checks 'userID==session.userID' that you can. Prepared
   Statements are the followon way of defending against SQL injection, as the
  -JDBC runtime handles escaping of things. Dont try and build SQL strings
  +JDBC runtime handles escaping of things. Don't try and build SQL strings
   by hand; it is a recipe for security holes. 
   Note that this would seem to argue strongly against mapping Session EJB
   objects to SOAP Endpoints. This is not the case. The Session bean must
   merely assume that all incoming data is untrusted, and so validate it
   all before processing further. This is exactly the kind of task a
  -<i>Service Layer</i> should be doing.
  +<a href="">
  +<i>Service Layer</i></a> should be doing.
   <h3>Cross Site Scripting</h3>
  @@ -221,7 +247,7 @@
   think Axis itself is vulnerable, because although it may include
   supplied data in a SOAPFault, this is displayed as XML, not HTML.
   Clients which don't distinguish the two could be an issue, as could
  -anything we missed, especially in GET handling.  
  +anything we missed, especially in GET handling. 
   <h2>Securing Axis</h2>
  @@ -237,7 +263,7 @@
   <h3>Cut down the build</h3>
  -Rebuild Axis without bits of it you dont need. This is a very paranoid
  +Rebuild Axis without bits of it you don't need. This is a very paranoid
   solution, but keeps the number of potential attack points down. One area
   to consider is the 'instant SOAP service' feature of JWS pages. They,
   along with JSP pages, provide anyone who can get text files onto the web
  @@ -374,3 +400,16 @@
   security perspective, no security holes can exist for a system to be
   secure: no matter how obscure it is, someone may find it and exploit it.
   Be paranoid: you know it makes sense. 
  +Finally, don't get put off writing SOAP services through a fear of the
  +security implications. Any CGI-BIN or ASP/JSP page that takes parameters
  +is as much of a security risk as a SOAP endpoint. For some reason,
  +SOAP attracts dramatic press stories about infinite risk, perhaps
  +because it is new and unknown. It isn't: it is XML posted to a web
  +application, that's all. Only if you are scared of that, should you
  +not write a SOAP service. 

View raw message